Method and apparatus for cellular internet of things (ciot) data transfer over a control plane in a wireless communication system

ABSTRACT

A method, apparatus, and computer program product are provided for control plane cellular Internet of Things (CIoT) data transfer in a wireless communication system. A method for control plane messaging between a first entity and a second entity in a network in which control plane messages are sent in a control plane protocol is described. The method can include a service request procedure whereby the 5GMM mode is changed from 5GMM-IDLE to 5GMM-CONNECTED mode. In some embodiments, if a user equipment is using EPS services with control plane CIoT EPS optimization, this procedure can be used for UE initiated transfer of user data via the control plane. In some embodiments, the method can include receiving from a user equipment (UE), at a core access and mobility management function, a control plane service request message, starting a T3517 timer and enter the state 5GMM-SERVICE-REQUEST-INITIATED, and changing a 5GMM mode from a 5GMM-IDLE mode to a 5GMM-CONNECTED mode.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. Non-Provisional patentapplication Ser. No. 16/837,047, filed Apr. 1, 2020 and entitled “Methodand Apparatus for Cellular Internet of Things (CIoT) Data Transfer Overa Control Plane in a Wireless Communication System,” which claimspriority to, and the benefit of, U.S. Provisional Application Ser. No.62/828,223, filed Apr. 2, 2019, entitled “Method and Apparatus forCellular Internet of Things (CIoT) Data Transfer over a Control Plane ina Wireless Communication System” and also claims priority to, and thebenefit of, U.S. Provisional Application Ser. No. 62/833,334, filed Apr.12, 2019, entitled “Method And Apparatus For Cellular Internet of Things(CIoT) Data Transfer Over A Control Plane In A Wireless CommunicationSystem,” the entire disclosures of each of which are hereby incorporatedherein by reference in their entireties for all purposes.

TECHNICAL FIELD

An example embodiment relates generally to wireless communicationsystems, particularly to control plane Cellular Internet of Things(CIoT) data transfer in wireless communication systems.

BACKGROUND

In addition to traditional wireless communications systems andtelecommunications services, fifth-generation (5G) systems are expectedto support emerging use cases such as Internet of Things (IoT) andCellular IOT (CIoT) technologies, vehicle-to-vehicle/-infrastructurecommunication, tactile Internet, smart buildings, sensor networks, andthe like.

Currently there is no solution for supporting control plane CIoT datatransfer under planned 5G systems and protocols. Such solutions arerequired to enable user data transfer via control plane over 5Gconnections/systems.

BRIEF SUMMARY

A method, apparatus and computer program product are provided inaccordance with an example embodiment for control plane cellularInternet of Things (CIoT) data transfer in a wireless communicationsystem. A method for control plane messaging between a first entity anda second entity in a network in which control plane messages are sent ina control plane protocol is described. The method can include a servicerequest procedure whereby the 5GMM mode is changed from 5GMM-IDLE to5GMM-CONNECTED mode. In some embodiments, if a user equipment is usingEPS services with control plane CIoT EPS optimization, this procedurecan be used for UE initiated transfer of user data via the controlplane. In some embodiments, the method can include receiving from a userequipment (UE), at a core access and mobility management function, acontrol plane service request message, starting a T3517 timer and enterthe state 5GMM-SERVICE-REQUEST-INITIATED, and changing a 5GMM mode froma 5GMM-IDLE mode to a 5GMM-CONNECTED mode.

A method (e.g., a method of control plane messaging between a firstentity and a second entity in a network in which control plane messagesare sent in a control plane protocol) according to some embodiments ofthe present disclosure can include receiving from a user equipment (UE),at a core access and mobility management function, a control planeservice request message, starting a T3517 timer and entering a state as5GMM-SERVICE-REQUEST-INITIATED, and changing a 5GMM mode from a5GMM-IDLE mode to a 5GMM-CONNECTED mode. In some embodiments, the methodcan further include initiating transfer of user data via a controlplane. In some embodiments, the control plane service request message isreceived from user equipment (UE) in response to at least one of i) theUE is in a 5GMM-CONNECTED mode over a 3GPP access and receives a pagingrequest from the core access and mobility management function; ii) theUE, in 5GMM-CONNECTED mode over 3GPP access, receives a notificationfrom the network with access type indicating non-3GPP access; iii) theUE, in 5GMM-IDLE mode over 3GPP access, has uplink signalling pending;iv) the UE, in 5GMM-IDLE mode over 3GPP access, has uplink user datapending; v) the UE, in 5GMM-CONNECTED mode or in 5GMM-CONNECTED modewith RRC inactive indication, has user data pending due to no user-planeresources established for PDU session(s) used for user data transport;v) the UE in 5GMM-IDLE mode over non-3GPP access, receives an indicationfrom the lower layers of non-3GPP access, that the access stratumconnection is established between UE and network; vi) the UE, in5GMM-IDLE mode over 3GPP access, receives a notification from thenetwork with access type indicating 3GPP access when the UE is in5GMM-CONNECTED mode over non-3GPP access; vii) the UE, in 5GMM-IDLE,5GMM-CONNECTED mode over 3GPP access, or 5GMM-CONNECTED mode with RRCinactive indication, receives a request for emergency services fallbackfrom the upper layer and performs emergency services fallback; or viii)the UE, in 5GMM-CONNECTED mode over 3GPP access or in 5GMM-CONNECTEDmode with RRC inactive indication, receives a fallback indication fromthe lower layers and or the UE has a pending NAS procedure other than aregistration, service request, or de-registration procedure.

An apparatus according to some embodiments of the present disclosure caninclude at least one processor and at least one memory storing computerprogram code, the at least one memory and the computer program codeconfigured to, with the processor, cause the apparatus to receive from auser equipment (UE), at a core access and mobility management function,a control plane service request message, start a T3517 timer and enter astate as 5GMM-SERVICE-REQUEST-INITIATED, and change a 5GMM mode from a5GMM-IDLE mode to a 5GMM-CONNECTED mode. In some embodiments, the atleast one memory and the computer program code are further configuredto, with the processor, cause the apparatus to initiate transfer of userdata via a control plane. In some embodiments, the control plane servicerequest message is received from the UE in response to at least one ofi) the UE is in a 5GMM-CONNECTED mode over a 3GPP access and receives apaging request from the core access and mobility management function;ii) the UE, in 5GMM-CONNECTED mode over 3GPP access, receives anotification from the network with access type indicating non-3GPPaccess; iii) the UE, in 5GMM-IDLE mode over 3GPP access, has uplinksignalling pending; iv) the UE, in 5GMM-IDLE mode over 3GPP access, hasuplink user data pending; v) the UE, in 5GMM-CONNECTED mode or in5GMM-CONNECTED mode with RRC inactive indication, has user data pendingdue to no user-plane resources established for PDU session(s) used foruser data transport; v) the UE in 5GMM-IDLE mode over non-3GPP access,receives an indication from the lower layers of non-3GPP access, thatthe access stratum connection is established between UE and network; vi)the UE, in 5GMM-IDLE mode over 3GPP access, receives a notification fromthe network with access type indicating 3GPP access when the UE is in5GMM-CONNECTED mode over non-3GPP access; vii) the UE, in 5GMM-IDLE,5GMM-CONNECTED mode over 3GPP access, or 5GMM-CONNECTED mode with RRCinactive indication, receives a request for emergency services fallbackfrom the upper layer and performs emergency services fallback; or viii)the UE, in 5GMM-CONNECTED mode over 3GPP access or in 5GMM-CONNECTEDmode with RRC inactive indication, receives a fallback indication fromthe lower layers and or the UE has a pending NAS procedure other than aregistration, service request, or de-registration procedure.

An apparatus according to some embodiments of the present disclosure caninclude means, such as an apparatus including a core access and mobilitymanagement function and/or a processor and a memory storing computerprogram code, for receiving from a user equipment (UE), a control planeservice request message, starting a T3517 timer and entering a state as5GMM-SERVICE-REQUEST-INITIATED, and changing a 5GMM mode from a5GMM-IDLE mode to a 5GMM-CONNECTED mode. In some embodiments, theapparatus can further include means for initiating transfer of user datavia a control plane. In some embodiments, the control plane servicerequest message can be received from the UE in response to at least oneof i) the UE is in a 5GMM-CONNECTED mode over a 3GPP access and receivesa paging request from the core access and mobility management function;ii) the UE, in 5GMM-CONNECTED mode over 3GPP access, receives anotification from the network with access type indicating non-3GPPaccess; iii) the UE, in 5GMM-IDLE mode over 3GPP access, has uplinksignalling pending; iv) the UE, in 5GMM-IDLE mode over 3GPP access, hasuplink user data pending; v) the UE, in 5GMM-CONNECTED mode or in5GMM-CONNECTED mode with RRC inactive indication, has user data pendingdue to no user-plane resources established for PDU session(s) used foruser data transport; v) the UE in 5GMM-IDLE mode over non-3GPP access,receives an indication from the lower layers of non-3GPP access, thatthe access stratum connection is established between UE and network; vi)the UE, in 5GMM-IDLE mode over 3GPP access, receives a notification fromthe network with access type indicating 3GPP access when the UE is in5GMM-CONNECTED mode over non-3GPP access; vii) the UE, in 5GMM-IDLE,5GMM-CONNECTED mode over 3GPP access, or 5GMM-CONNECTED mode with RRCinactive indication, receives a request for emergency services fallbackfrom the upper layer and performs emergency services fallback; or viii)the UE, in 5GMM-CONNECTED mode over 3GPP access or in 5GMM-CONNECTEDmode with RRC inactive indication, receives a fallback indication fromthe lower layers and or the UE has a pending NAS procedure other than aregistration, service request, or de-registration procedure.

A computer program product according to some embodiments of the presentdisclosure can include a non-transitory computer-readable storage mediumhaving stored thereon computer-readable code, which, when executed by atleast one processor, causes the at least one processor to receive from auser equipment (UE), at a core access and mobility management function,a control plane service request message, start a T3517 timer and enter astate as 5GMM-SERVICE-REQUEST-INITIATED, and change a 5GMM mode from a5GMM-IDLE mode to a 5GMM-CONNECTED mode. In some embodiments, executionof the computer-readable code by the at least one processor furthercauses the at least one processor to initiate transfer of user data viaa control plane. In some embodiments, the control plane service requestmessage can be received from the UE in response to at least one of i)the UE is in a 5GMM-CONNECTED mode over a 3GPP access and receives apaging request from the core access and mobility management function;ii) the UE, in 5GMM-CONNECTED mode over 3GPP access, receives anotification from the network with access type indicating non-3GPPaccess; iii) the UE, in 5GMM-IDLE mode over 3GPP access, has uplinksignalling pending; iv) the UE, in 5GMM-IDLE mode over 3GPP access, hasuplink user data pending; v) the UE, in 5GMM-CONNECTED mode or in5GMM-CONNECTED mode with RRC inactive indication, has user data pendingdue to no user-plane resources established for PDU session(s) used foruser data transport; v) the UE in 5GMM-IDLE mode over non-3GPP access,receives an indication from the lower layers of non-3GPP access, thatthe access stratum connection is established between UE and network; vi)the UE, in 5GMM-IDLE mode over 3GPP access, receives a notification fromthe network with access type indicating 3GPP access when the UE is in5GMM-CONNECTED mode over non-3GPP access; vii) the UE, in 5GMM-IDLE,5GMM-CONNECTED mode over 3GPP access, or 5GMM-CONNECTED mode with RRCinactive indication, receives a request for emergency services fallbackfrom the upper layer and performs emergency services fallback; or viii)the UE, in 5GMM-CONNECTED mode over 3GPP access or in 5GMM-CONNECTEDmode with RRC inactive indication, receives a fallback indication fromthe lower layers and or the UE has a pending NAS procedure other than aregistration, service request, or de-registration procedure.

In some embodiments, a method can be provided for control planemessaging between a first entity and a second entity in a network inwhich control plane messages are sent in a control plane protocol, themethod comprising: sending from a user equipment (UE) to a core accessand mobility management function (AMF), a control plane service requestmessage; starting a T3517 timer and entering a service request initiatedstate; and changing a mode of the UE from an idle mode to a connectedmode. In some embodiments, the method can further comprise: initiatingtransfer of user data, from the UE to the AMF, via a control plane. Insome embodiments, the user data comprises cellular internet-of-things(CIoT) user data in a CIoT user data container, stored within a payload.In some embodiments, the method can further comprise: including one ormore protocol data unit (PDU) session identifications and one or morerelease assistance indications in the payload; indicating a payloadcontainer type in a payload container type information element (IE) ofthe payload, wherein the payload container type is a CIoT user datacontainer type; indicating the payload container type to a user datacontainer of the payload; and sending an uplink non-access stratumtransport message to the AMF. In some embodiments, the control planeservice request message is sent from the UE to the AMF in response toeither: the UE being in the connected mode over 3GPP access and the UEreceiving a paging request from the AMF, the UE being in the connectedmode over 3GPP access and receiving a notification from the AMF with anaccess type indicating non-3GPP access, the UE being in the idle modeover 3GPP access and having uplink signalling pending, the UE being inthe idle mode over 3GPP access and having uplink user data pending, theUE being in the connected mode, or in the connected mode with a radioresource control (RRC) inactive indication, and having user data pendingdue to no user-plane resources being established for one or moreprotocol data unit (PDU) sessions used for user data transport, the UEbeing in the idle mode over non-3GPP access and receiving an indicationfrom lower layers of the non-3GPP access, wherein an access stratumconnection is established between the UE and the AMF, the UE being inthe idle mode over 3GPP access and receiving a notification from the AMFwith access type indicating 3GPP access when the UE is in the connectedmode over non-3GPP access, or the UE being in the idle mode, in theconnected mode over 3GPP access, or in the connected mode with the RRCinactive indication, and in response to receiving a request foremergency services fallback from one or more upper layers of the 3GPPaccess. In some embodiments, the control plane service request messageis sent from the UE to the AMF in response to the UE being in the idlemode, in the connected mode over 3GPP access, or in the connected modewith the RRC inactive indication, and in response to receiving therequest for emergency services fallback from the one or more upperlayers of the 3GPP access, wherein the method further comprises:performing emergency services fallback. In some embodiments, the controlplane service request message is sent from the UE to the AMF in responseto the UE being in the connected mode over 3GPP access or in theconnected mode with a radio resource control (RRC) inactive indication,and in response to the UE receiving a fallback indication from one ormore lower layers of the 3GPP access, or when the UE has a pending NASprocedure other than a registration procedure, a service requestprocedure, or a de-registration procedure.

In some embodiments, a method can be provided for control planemessaging between entities in a network in which control plane messagesare sent according to a control plane protocol, the method comprising:receiving, from a user equipment (UE) or a session management function(SMF), at a core access and mobility management function (AMF), acontrol plane service request message; and, in an instance in which theAMF determines, based upon the control plane service request message,that the UE satisfies one or more conditions, sending, by the AMF, tothe UE or the SMF, a service accept message. In some embodiments, themethod can further comprise: receiving, at the AMF, from the UE or SMF,user data via a control plane; and initiating, based upon the controlplane service request message and the user data, an authentication andkey agreement procedure or an extensible authentication protocol. Insome embodiments, the user data comprises cellular internet-of-things(CIoT) user data in a CIoT user data container, stored within a payload.In some embodiments, the payload further comprises one or more protocoldata unit (PDU) session identifications and one or more releaseassistance indications in the payload, wherein a payload container typeis indicated in a payload container type information element (IE) of thepayload as being a CIoT user data container type, and wherein thepayload container type is indicated to a user data container of thepayload, the method further comprising: receiving, from the UE, anuplink non-access stratum transport message. In some embodiments, themethod can further comprise: identifying a PDU session routing contextfor the UE and the PDU session identification; and forwarding the PDUsession routing context of a payload container IE towards a sessionmanagement function (SMF) identified by the PDU session routing context.In some embodiments, the method can further comprise: in an instance inwhich a release assistance indication IE is included in the uplinknon-access stratum transport message received from the UE, a downlinkdata expected (DDX) field of the release assistance indication IEindicates that no further uplink and no further downlink datatransmission subsequent to the uplink data transmission is expected, andthere is no downlink signalling or downlink data for the UE, initiatingrelease of a connection and mobility management (N1) interface on anon-access stratum signaling connection.

In some embodiments, an apparatus can be provided that comprises atleast one processor and at least one memory storing computer programcode, the at least one memory and the computer program code configuredto, with the at least one processor, cause the apparatus to: send, to acore access and mobility management function (AMF), a control planeservice request message; start a T3517 timer and enter a service requestinitiated state; and change a mode of the apparatus from an idle mode toa connected mode. In some embodiments, the at least one memory and thecomputer program code are further configured to, with the at least oneprocessor, cause the apparatus to: initiate transfer of user data, tothe AMF, via a control plane, wherein said user data comprises cellularinternet-of-things (CIoT) user data in a CIoT user data container,stored within a payload. In some embodiments, the at least one memoryand the computer program code are further configured to, with the atleast one processor, cause the apparatus to: include one or moreprotocol data unit (PDU) session identifications and one or more releaseassistance indications in the payload; indicate a payload container typein a payload container type information element (IE) of the payload,wherein the payload container type is a CIoT user data container type;indicate the payload container type to a user data container of thepayload; and send an uplink non-access stratum transport message to theAMF.

In some embodiments, an apparatus can be provided that comprises atleast one processor and at least one memory storing computer programcode, the at least one memory and the computer program code configuredto, with the at least one processor, cause the apparatus to: receive,from a user equipment (UE) or a session management function (SMF), atthe apparatus, a control plane service request message; and, in aninstance in which the apparatus determines, based upon the control planeservice request message, that the UE satisfies one or more conditions,send, to the UE or the SMF, a service accept message. In someembodiments, the at least one memory and the computer program code arefurther configured to, with the at least one processor, cause theapparatus to: receive, from the UE or SMF, user data via a controlplane; and initiate, based upon the control plane service requestmessage and the user data, an authentication and key agreement procedureor an extensible authentication protocol, wherein said user datacomprises cellular internet-of-things (CIoT) user data in a CIoT userdata container, stored within a payload.

In some embodiments, a computer program product can be provided thatcomprises a non-transitory computer-readable storage medium havingstored thereon computer-readable code, which, when executed by at leastone processor, causes the at least one processor to: send, from a userequipment (UE), to a core access and mobility management function, acontrol plane service request message; start a T3517 timer and enter aservice request initiated state; and change a mode of the UE from anidle mode to a connected mode.

In some embodiments, a computer program product can be provided thatcomprises a non-transitory computer-readable storage medium havingstored thereon computer-readable code, which, when executed by at leastone processor, causes the at least one processor to: receive, from auser equipment (UE) or a session management function (SMF), at a coreaccess and mobility management function (AMF), a control plane servicerequest message; and, in an instance in which the AMF determines, basedupon the control plane service request message, that the UE satisfiesone or more conditions, cause the AMF to send, to the UE or the SMF, aservice accept message.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described certain example embodiments of the presentdisclosure in general terms, reference will hereinafter be made to theaccompanying drawings, which are not necessarily drawn to scale, andwherein:

FIG. 1 is a block diagram of an apparatus that may be specificallyconfigured in accordance with an example embodiment of the presentinvention;

FIG. 2 is a flowchart illustrating a set of operations performed, suchas by the apparatus of FIG. 1, in accordance with an example embodimentof the present invention;

FIG. 3 is a graphical representation of messages sent between entitiesin a 5G network, in accordance with an example embodiment of the presentinvention;

FIG. 4 is a graphical representation of a process for uplink datatransfer via control plane to a data network over an N6 interface in a5G system, in accordance with an example embodiment of the presentinvention;

FIG. 5 is a graphical representation of a process for downlink datatransfer via control plane to a data network over an N6 interface in a5G system, in accordance with an example embodiment of the presentinvention;

FIG. 6 is an example procedure for encoding an information element fortransport with one or more payloads, such as by the apparatus of FIG. 1,in accordance with an example embodiment of the present invention;

FIG. 7 is an example of a CIoT user data container configured toindicate a type of payload included in a payload container informationelement, in accordance with an example embodiment of the presentinvention;

FIG. 8 is a graphical representation of a process for uplink datatransfer via control plane to a data network over N6 interface for userequipment in IDLE mode, in accordance with an example embodiment of thepresent invention;

FIG. 9 is a graphical representation of a process for uplink transfer ofmultiple user data and SMS messages via control plane for user equipmentin IDLE mode, in accordance with an example embodiment of the presentinvention;

FIG. 10 is a graphical representation of a process for downlink datatransfer via control plane for user equipment in IDLE mode, inaccordance with an example embodiment of the present invention;

FIG. 11 is a graphical representation of a process for downlink transferof multiple user data and SMS messages via control plane for userequipment in IDLE mode, in accordance with an example embodiment of thepresent invention;

FIG. 12 is a graphical representation of a process for uplink datatransfer via control plane for user equipment in CONNECTED mode, inaccordance with an example embodiment of the present invention;

FIG. 13 is a graphical representation of a process for uplink transferof multiple user data and SMS messages via control plane for userequipment in CONNECTED mode, in accordance with an example embodiment ofthe present invention;

FIG. 14 is a graphical representation of a process for downlink datatransfer via control plane for user equipment in CONNECTED mode, inaccordance with an example embodiment of the present invention;

FIG. 15 is a graphical representation of a process for downlink transferof multiple user data and SMS messages via control plane for userequipment in CONNECTED mode, in accordance with an example embodiment ofthe present invention;

FIG. 16 is a graphical representation of a process for uplink SMSmessages transfer via control plane for user equipment in IDLE mode, inaccordance with an example embodiment of the present invention;

FIG. 17 is a graphical representation of a process for downlink SMSmessages transfer via control plane for user equipment in IDLE mode, inaccordance with an example embodiment of the present invention;

FIG. 18 is a representation of a user data container informationelement, in accordance with an example embodiment of the presentinvention;

FIG. 19 is a representation of a NAS message container informationelement, in accordance with an example embodiment of the presentinvention; and

FIG. 20 is a representation of a control plane service type informationelement, in accordance with an example embodiment of the presentinvention.

DETAILED DESCRIPTION

Some embodiments will now be described more fully hereinafter withreference to the accompanying drawings, in which some, but not all,embodiments of the invention are shown. Indeed, various embodiments ofthe invention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like reference numerals refer to like elementsthroughout. As used herein, the terms “data,” “content,” “information,”and similar terms may be used interchangeably to refer to data capableof being transmitted, received and/or stored in accordance withembodiments of the present invention. Thus, use of any such terms shouldnot be taken to limit the spirit and scope of embodiments of the presentinvention.

Additionally, as used herein, the term ‘circuitry’ refers to (a)hardware-only circuit implementations (e.g., implementations in analogcircuitry and/or digital circuitry); (b) combinations of circuits andcomputer program product(s) comprising software and/or firmwareinstructions stored on one or more computer readable memories that worktogether to cause an apparatus to perform one or more functionsdescribed herein; and (c) circuits, such as, for example, amicroprocessor(s) or a portion of a microprocessor(s), that requiresoftware or firmware for operation even if the software or firmware isnot physically present. This definition of ‘circuitry’ applies to alluses of this term herein, including in any claims. As a further example,as used herein, the term ‘circuitry’ also includes an implementationcomprising one or more processors and/or portion(s) thereof andaccompanying software and/or firmware. As another example, the term‘circuitry’ as used herein also includes, for example, a basebandintegrated circuit or applications processor integrated circuit for amobile phone or a similar integrated circuit in a server, a cellularnetwork device, other network device, and/or other computing device.

As defined herein, a “computer-readable storage medium,” which refers toa non-transitory physical storage medium (e.g., volatile or non-volatilememory device), can be differentiated from a “computer-readabletransmission medium,” which refers to an electromagnetic signal. Such amedium may take many forms, including, but not limited to anon-transitory computer-readable storage medium (e.g., non-volatilemedia, volatile media), and transmission media. Transmission mediainclude, for example, coaxial cables, copper wire, fiber optic cables,and carrier waves that travel through space without wires or cables,such as acoustic waves and electromagnetic waves, including radio,optical and infrared waves. Signals include man-made transientvariations in amplitude, frequency, phase, polarization or otherphysical properties transmitted through the transmission media. Examplesof non-transitory computer-readable media include a magnetic computerreadable medium (e.g., a floppy disk, hard disk, magnetic tape, anyother magnetic medium), an optical computer readable medium (e.g., acompact disc read only memory (CD-ROM), a digital versatile disc (DVD),a Blu-Ray disc, or the like), a random access memory (RAM), aprogrammable read only memory (PROM), an erasable programmable read onlymemory (EPROM), a FLASH-EPROM, or any other non-transitory medium fromwhich a computer can read. The term computer-readable storage medium isused herein to refer to any computer-readable medium except transmissionmedia. However, it will be appreciated that where embodiments aredescribed to use a computer-readable storage medium, other types ofcomputer-readable mediums may be substituted for or used in addition tothe computer-readable storage medium in alternative embodiments.

While various inventive embodiments have been described and illustratedherein, those of ordinary skill in the art will readily envision avariety of other means and/or structures for performing the functionand/or obtaining the results and/or one or more of the advantagesdescribed herein, and each of such variations and/or modifications isdeemed to be within the scope of the inventive embodiments describedherein. More generally, those skilled in the art will readily appreciatethat all parameters, dimensions, materials, and configurations describedherein are meant to be examples and that the actual parameters,dimensions, materials, and/or configurations will depend upon thespecific application or applications for which the inventive teachingsis/are used. Those skilled in the art will recognize, or be able toascertain using no more than routine experimentation, many equivalentsto the specific inventive embodiments described herein. It is,therefore, to be understood that the foregoing embodiments are presentedby way of example only and that, within the scope of the appended claimsand equivalents thereto, inventive embodiments may be practicedotherwise than as specifically described and claimed. Inventiveembodiments of the present disclosure are directed to each individualfeature, system, article, material, kit, and/or method described herein.In addition, any combination of two or more such features, systems,articles, materials, kits, and/or methods, if such features, systems,articles, materials, kits, and/or methods are not mutually inconsistent,is included within the inventive scope of the present disclosure.

Referring now to FIG. 1, an example of an apparatus and system forcarrying out the methods, processes, and approaches described herein isprovided. It will be appreciated that the apparatus 100 is provided asan example of one embodiment and should not be construed to narrow thescope or spirit of the invention in any way. In this regard, the scopeof the disclosure encompasses many potential embodiments in addition tothose illustrated and described herein. As such, while FIG. 1illustrates one example of a configuration of an apparatus for carryingout control plane CIoT data transfer in a wireless communication system,such as a 5G system, other configurations may also be used to implementcertain embodiments of the present disclosure.

The apparatus 100 may be embodied as a desktop computer, laptopcomputer, mobile terminal, mobile computer, mobile phone, mobilecommunication device, game device, digital camera/camcorder, audio/videoplayer, television device, radio receiver, digital video recorder,positioning device, a chipset, a computing device comprising a chipset,any combination thereof, and/or the like. In some example embodiments,the apparatus 100 is embodied as a mobile computing device, such asmobile telephones, mobile computers, personal digital assistants (PDAs),pagers, laptop computers, desktop computers, gaming devices,televisions, e-papers, and other types of electronic systems, which mayemploy various embodiments of the invention.

The apparatus 100 can include a computing device 102 including aprocessor 104, and storage, such as a non-volatile memory 106 and/orvolatile memory 108. In some embodiments, the processor 104 may, forexample, be embodied as various means including circuitry, one or moremicroprocessors with accompanying digital signal processor(s), one ormore processor(s) without an accompanying digital signal processor, oneor more coprocessors, one or more multi-core processors, one or morecontrollers, processing circuitry, one or more computers, various otherprocessing elements including integrated circuits such as, for example,an ASIC (application specific integrated circuit) or FPGA (fieldprogrammable gate array), or some combination thereof. Accordingly,although illustrated in FIG. 1 as a single processor, in someembodiments the processor 104 comprises a plurality of processors. Thesesignals sent and received by the processor 104 may include signalinginformation in accordance with an air interface standard of anapplicable cellular system, and/or any number of different wireline orwireless networking techniques, comprising but not limited to Wi-Fi,wireless local access network (WLAN) techniques such as Institute ofElectrical and Electronics Engineers (IEEE) 802.11, 802.16, and/or thelike. In addition, these signals may include speech data, user generateddata, user requested data, and/or the like. In this regard, the mobileterminal may be capable of operating with one or more air interfacestandards, communication protocols, modulation types, access types,and/or the like. More particularly, the mobile terminal may be capableof operating in accordance with various first generation (1G), secondgeneration (2G), 2.5G, third-generation (3G) communication protocols,fourth-generation (4G) communication protocols, fifth-generation (5G),Internet Protocol Multimedia Subsystem (IMS) communication protocols(e.g., session initiation protocol (SIP)), and/or the like. For example,the mobile terminal may be capable of operating in accordance with 2Gwireless communication protocols IS-136 (Time Division Multiple Access(TDMA)), Global System for Mobile communications (GSM), IS-95 (CodeDivision Multiple Access (CDMA)), and/or the like. Also, for example,the mobile terminal may be capable of operating in accordance with 2.5Gwireless communication protocols General Packet Radio Service (GPRS),Enhanced Data GSM Environment (EDGE), and/or the like. Further, forexample, the mobile terminal may be capable of operating in accordancewith 3G wireless communication protocols such as Universal MobileTelecommunications System (UMTS), Code Division Multiple Access 2000(CDMA2000), Wideband Code Division Multiple Access (WCDMA), TimeDivision-Synchronous Code Division Multiple Access (TD-SCDMA), and/orthe like. The mobile terminal may be additionally capable of operatingin accordance with 3.9G wireless communication protocols such as LongTerm Evolution (LTE) or Evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN) and/or the like. Additionally, for example, the mobileterminal may be capable of operating in accordance withfourth-generation (4G) wireless communication protocols and/or the likeas well as similar wireless communication protocols that may bedeveloped in the future.

Some Narrow-band Advanced Mobile Phone System (NAMPS), as well as TotalAccess Communication System (TACS), mobile terminals may also benefitfrom embodiments of this invention, as should dual or higher mode phones(e.g., digital/analog or TDMA/CDMA/analog phones). Additionally, theapparatus 100 or a component thereof may be capable of operatingaccording to Wi-Fi or Worldwide Interoperability for Microwave Access(WiMAX) protocols.

It is understood that the processor 104 may comprise circuitry forimplementing audio/video and logic functions of the apparatus 100. Forexample, the processor 104 may comprise a digital signal processordevice, a microprocessor device, an analog-to-digital converter, adigital-to-analog converter, and/or the like. Control and signalprocessing functions of the mobile terminal may be allocated betweenthese devices according to their respective capabilities. The processormay additionally comprise an internal voice coder (VC), an internal datamodem (DM), and/or the like. Further, the processor may comprisefunctionality to operate one or more software programs, which may bestored in memory. For example, the processor 104 may be capable ofoperating a connectivity program, such as a web browser. Theconnectivity program may allow the apparatus 100 to transmit and receiveweb content, such as location-based content, according to a protocol,such as Wireless Application Protocol (WAP), hypertext transfer protocol(HTTP), and/or the like. The apparatus 100 may be capable of using aTransmission Control Protocol/Internet Protocol (TCP/IP) to transmit andreceive web content across the internet or other networks.

The apparatus 100 may also comprise a user interface 112 including, forexample, an earphone or speaker, a ringer, a microphone, a user display,a user input interface, and/or the like, which may be operationallycoupled to the processor 104. In this regard, the processor 104 maycomprise user interface circuitry configured to control at least somefunctions of one or more elements of the user interface, such as, forexample, the speaker, the ringer, the microphone, the display, and/orthe like. The processor 104 and/or user interface circuitry comprisingthe processor 104 may be configured to control one or more functions ofone or more elements of the user interface through computer programinstructions (e.g., software and/or firmware) stored on a memoryaccessible to the processor 104 (e.g., non-volatile memory 106, volatilememory 108, and/or the like). Although not shown, the apparatus 100 maycomprise a battery for powering various circuits related to theapparatus 100, for example, a circuit to provide mechanical vibration asa detectable output. The apparatus 100 can further comprise a display114. In some embodiments, the display 114 may be of any type appropriatefor the electronic device in question with some examples including aplasma display panel (PDP), a liquid crystal display (LCD), alight-emitting diode (LED), an organic light-emitting diode display(OLED), a projector, a holographic display, or the like. The userinterface 112 may comprise devices allowing the apparatus 100 to receivedata, such as a keypad, a touch display (e.g., some example embodimentswherein the display 114 is configured as a touch display), a joystick(not shown), and/or other input device. In embodiments including akeypad, the keypad may comprise numeric (0-9) and related keys (#, *),and/or other keys for operating the apparatus 100.

The apparatus 100 may comprise memory, such as the non-volatile memory106 and/or the volatile memory 108, such as RAM, read only memory (ROM),non-volatile RAM (NVRAM), a subscriber identity module (SIM), aremovable user identity module (R-UIM), and/or the like. In addition tothe memory, the apparatus 100 may comprise other removable and/or fixedmemory. In some embodiments, the volatile memory 108 may include RandomAccess Memory (RAM) including dynamic and/or static RAM, on-chip oroff-chip cache memory, and/or the like. In some embodiments, thenon-volatile memory 106, which may be embedded and/or removable, mayinclude, for example, read-only memory, flash memory, magnetic storagedevices (e.g., hard disks, floppy disk drives, magnetic tape, etc.),optical disc drives and/or media, non-volatile random access memory(NVRAM), and/or the like. Like the volatile memory 108, the non-volatilememory 106 may include a cache area for temporary storage of data. Thememories may store one or more software programs, instructions, piecesof information, data, and/or the like which may be used by the mobileterminal for performing functions of the mobile terminal. For example,the memories may comprise an identifier, such as an international mobileequipment identification (IMEI) code, capable of uniquely identifyingthe apparatus 100.

Returning to FIG. 1, in an example embodiment, the apparatus 100includes various means for performing the various functions hereindescribed. These means may comprise one or more of the processor 104,the non-volatile memory 106, the volatile memory 108, the user interface112, or the display 114. The means of the apparatus 100 as describedherein may be embodied as, for example, circuitry, hardware elements(e.g., a suitably programmed processor, combinational logic circuit,and/or the like), a computer program product comprisingcomputer-readable program instructions (e.g., software or firmware)stored on a computer-readable medium (e.g., storage 106 or 108) that isexecutable by a suitably configured processing device (e.g., theprocessor 104), or some combination thereof.

In some example embodiments, one or more of the means illustrated inFIG. 1 may be embodied as a chip or chip set. In other words, theapparatus 100 may comprise one or more physical packages (e.g., chips)including materials, components and/or wires on a structural assembly(e.g., a baseboard). The structural assembly may provide physicalstrength, conservation of size, and/or limitation of electricalinteraction for component circuitry included thereon. In this regard,the processor 104, the memory 106 and/or 108, the user interface 112,and/or the display 114 may be embodied as a chip or chip set. Theapparatus 100 may therefore, in some cases, be configured to or maycomprise component(s) configured to implement embodiments of the presentinvention on a single chip or as a single “system on a chip.” As such,in some cases, a chip or chipset may constitute means for performing oneor more operations for providing the functionalities described herein.

The processor 104 may, for example, be embodied as various meansincluding one or more microprocessors with accompanying digital signalprocessor(s), one or more processor(s) without an accompanying digitalsignal processor, one or more coprocessors, one or more multi-coreprocessors, one or more controllers, processing circuitry, one or morecomputers, various other processing elements including integratedcircuits such as, for example, an ASIC (application specific integratedcircuit) or FPGA (field programmable gate array), one or more othertypes of hardware processors, or some combination thereof. Accordingly,although illustrated in FIG. 1 as a single processor, in someembodiments the processor 104 comprises a plurality of processors. Theplurality of processors may be in operative communication with eachother and may be collectively configured to perform one or morefunctionalities of the apparatus 100 as described herein. The pluralityof processors may be embodied on a single computing device ordistributed across a plurality of computing devices collectivelyconfigured to function as the apparatus 100. In embodiments wherein theapparatus 100 is embodied as an apparatus 100, the processor 104 may beembodied as or comprise the processor 104 (shown in FIG. 1). In someexample embodiments, the processor 104 is configured to executeinstructions stored in the memory 106 and/or 108 or otherwise accessibleto the processor 104. These instructions, when executed by the processor104, may cause the apparatus 100 to perform one or more of thefunctionalities of the apparatus 100 as described herein. As such,whether configured by hardware or software methods, or by a combinationthereof, the processor 104 may comprise an entity capable of performingoperations according to embodiments of the present invention whileconfigured accordingly. Thus, for example, when the processor 104 isembodied as an ASIC, FPGA or the like, the processor 104 may comprisespecifically configured hardware for conducting one or more operationsdescribed herein. Alternatively, as another example, when the processor104 is embodied as an executor of instructions, such as may be stored inthe memory 106 and/or 108, the instructions may specifically configurethe processor 104 to perform one or more algorithms and operationsdescribed herein.

The memory 106 and/or 108 may comprise, for example, volatile memory,non-volatile memory, or some combination thereof. In this regard, thememory 106 and/or 108 may comprise a non-transitory computer-readablestorage medium. Although illustrated in FIG. 1 as a single memory, thememory 106 and/or 108 may comprise a plurality of memories. Theplurality of memories may be embodied on a single computing device ormay be distributed across a plurality of computing devices collectivelyconfigured to function as the apparatus 100. In various exampleembodiments, the memory 106 and/or 108 may comprise a hard disk, randomaccess memory, cache memory, flash memory, a compact disc read onlymemory (CD-ROM), digital versatile disc read only memory (DVD-ROM), anoptical disc, circuitry configured to store information, or somecombination thereof. In some embodiments, the memory 106 and/or 108 maycomprise the volatile memory 108 and/or the non-volatile memory 106(shown in FIG. 1). The memory 106 and/or 108 may be configured to storeinformation, data, applications, instructions, or the like for enablingthe apparatus 100 to carry out various functions in accordance withvarious example embodiments. For example, in some example embodiments,the memory 106 and/or 108 is configured to buffer input data forprocessing by the processor 104. Additionally or alternatively, thememory 106 and/or 108 may be configured to store program instructionsfor execution by the processor 104. The memory 106 and/or 108 may storeinformation in the form of static and/or dynamic information. The storedinformation may include, for example, images, content, media content,user data, application data, and/or the like. This stored informationmay be stored and/or used by the processor 104 during the course ofperforming its functionalities.

In some embodiments, the apparatus 100 can further comprise acommunication interface (not shown) that may be embodied as any deviceor means embodied in circuitry, hardware, a computer program productcomprising computer readable program instructions stored on a computerreadable medium (e.g., the memory 106 and/or 108) and executed by aprocessing device (e.g., the processor 104), or a combination thereofthat is configured to receive and/or transmit data from/to anothercomputing device. In some example embodiments, the communicationinterface is at least partially embodied as or otherwise controlled bythe processor 104. In this regard, the communication interface may be incommunication with the processor 104, such as via a bus. Thecommunication interface may include, for example, an antenna, atransmitter, a receiver, a transceiver and/or supporting hardware orsoftware for enabling communications with one or more remote computingdevices. In embodiments wherein the apparatus 100 is embodied as anapparatus 100, the communication interface may be embodied as orcomprise the transmitter and the receiver. The communication interfacemay be configured to receive and/or transmit data using any protocolthat may be used for communications between computing devices. In thisregard, the communication interface may be configured to receive and/ortransmit data using any protocol that may be used for transmission ofdata over a wireless network, wireline network, some combinationthereof, or the like by which the apparatus 100 and one or morecomputing devices may be in communication. As an example, thecommunication interface may be configured to receive and/or otherwiseaccess content (e.g., web page content, streaming media content, and/orthe like) over a network from a server or other content source. Thecommunication interface may additionally be in communication with thememory 106 and/or 108, user interface 112 and/or the processor 104, suchas via a bus.

The user interface 112 may be in communication with the processor 104and configured to receive an indication of a user input and/or toprovide an audible, visual, mechanical, or other output to a user. Assuch, the user interface 112 may include, for example, a keyboard, amouse, a joystick, a display, a touch screen display, a microphone, aspeaker, and/or other input/output mechanisms. In embodiments whereinthe apparatus 100 is embodied as an apparatus 100, the user interface112 may be embodied as or comprise the user input interface, such as thedisplay 114 (shown in FIG. 1), and other components such as a keypad,mouse, etc. The user interface 112 may be in communication with thememory 106 and/or 108, communication interface, a sensor, a speaker,and/or the processor 104, such as via a bus. In some exampleembodiments, the user interface 112 may comprise a single input/outputmechanism. In other embodiments, the user interface 112 may comprise acontent display and touch display, such as the display 114. In someembodiments, the user interface 112 may comprise a touch display userinterface with a content display portion and a dedicated user inputportion, such as a virtual keyboard, virtual plano, or an applicationwith a designated key for user input.

The processor 104 may be embodied as various means, such as circuitry,hardware, a computer program product comprising computer readableprogram instructions stored on a computer readable medium (e.g., thememory 106 and/or 108) and executed by a processing device (e.g., theprocessor 104), or some combination thereof and, in some embodiments, isembodied as or otherwise controlled by the processor 104. The processor104 may further be in communication with one or more of the memory 106and/or 108, or user interface 112, such as via a bus.

The processor 104 may be configured to receive a user input from a userinterface 112, such as a touch display. The user input or signal maycarry positional information indicative of the user input. In thisregard, the position may comprise a position of the user input in atwo-dimensional space, which may be relative to the surface of the touchdisplay user interface. For example, the position may comprise acoordinate position relative to a two-dimensional coordinate system(e.g., an X and Y axis), such that the position may be determined.Accordingly, the processor 104 may determine anelement/instruction/command that corresponds with a key, or image,displayed on the touch display user interface at the determined positionor within a predefined proximity (e.g., within a predefined tolerancerange) of the determined position. The processor 104 may be furtherconfigured to perform a function or action related to the keycorresponding to the element/instruction/command determined by theprocessor 104 based on the position of the touch or other user input.

As described herein, NB-N1 mode indicates that the correspondingdisclosure applies only to a system which operates in NB-N1 mode. For amulti-access system this case applies if the current serving radioaccess network provides access to 5G network services via E-UTRA byNB-IoT. In addition, WB-N1 mode indicates that the correspondingdisclosure applies only to a system which operates in WB-N1 mode. For amulti-access system this case applies if the system operates in N1 mode,but not in NB-N1 mode.

FIGS. 2 and 3 illustrate an example process for the transfer of UE userdata via control plane to a data network over an N6 interface in a 5Gsystem. As used herein, “5G system,” “5GS,” “5GMM,” “3GPP” and the likerefer to a fifth-generation wireless communication protocol.

A system 200 for cellular Information of Things (CIoT) data transferbetween user equipment 220 (UE 220) and a data network 227 is described.In some embodiments, the system 200 can introduce a new CONTROL PLANESERVICE REQUEST for initial NAS messages. In some embodiments, data canbe transmitted from user equipment 220 (UE 220) to an AMF 223 via a NextGeneration Radio Access Network 222 (NG-RAN 222) with a 3GPP Accessnumber 221. In some embodiments, upon receipt of the SERVICE REQUEST orCONTROL PLANE SERVICE REQUEST message from the US 220, the AMF 223 mayinitiate the common procedures, e.g., the 5G AKA based primaryauthentication and key agreement procedure or the EAP based primaryauthentication and key agreement procedure. A possible message paththrough the system 200 is illustrated as the dashed line identified as“UE user data transfer via control plane” in FIG. 2. The control planeroute (dashed line) can follow a path from the AMF 223 to a SessionManagement Function 224 (SMF 224), from the SMF 224 to a User PlaneFunction 226 UPF 226, and from the UPF 226 to the data network 227. Thesystem 200 can further include a n Authentication Server Function 210(AUSF 210), a Unified Data Management 212 (UDM 212), and a Unified DataRepository 214 (UDR 214), which can comprise an Authentication Server205 or the like. The system 200 can further include a Policy ControlFunction 225 (PCF 225). The system 200 or any component thereof can beembodied by the apparatus of FIG. 1 or any variant or component thereof.As such, the following description of processes and methods describesprocesses and methods that can likewise be carried out at least in partby the apparatus of FIG. 1 or any variant or component thereof.

The purpose of the service request procedure is to change the 5GMM modefrom 5GMM-IDLE to 5GMM-CONNECTED mode. If the UE is not using EPSservices with control plane CIoT EPS optimization, to request theestablishment of user-plane resources for PDU sessions which areestablished without user-plane resources. In latter case, the 5GMM modecan be the 5GMM-IDLE mode or the 5GMM-CONNECTED mode if the UE requiresto establish user-plane resources for PDU sessions. If the UE is usingEPS services with control plane CIoT EPS optimization, this procedurecan be used for UE initiated transfer of user data via the controlplane.

Referring now to FIG. 4, the uplink transfer of UE user data via controlplane to a data network over N6 interface in a 5G system is illustrated.In some embodiments, the process includes a UE registering with the AMFfor CIoT control plane optimizations (CP-CIoT). The process can furtherinclude establishment of a NAS Security Context at both the UE and AMFand ciphering and integrity protection at both the UE and AMF. Theprocess can further include the transmission from the UE to the AMF of aControl Plane Service Request (e.g., ngKSI, payload_container_type=“CIoTuser data container”, payload_container [user data, pdu session ID]).The process can further include selection by the AMF of an SMF capableof small data transfer via NAS. The process can further includetransmission of a Nsmf_PDUSession_DataTransfer Request (e.g.,payload_container (user data), PDU session ID) from the AMF to the SMF.The process can further include selection by the SMF of a UPF or NEF foruser data delivery based on configuration preferences orcompatabilities. The process can further include subsequently orsimultaneously with the “selection by the SMF of a UPF or NEF” stage,transmission by the AMF of a Service Accept message back to the UE. Theprocess can further include transmission by the SMF of aPFCP_data_forwarding (N4-tunnel ID, payload_container [user data])message to the UPF or NEF selected.

In some embodiments, a service request procedure can be initiated whenthe UE is not using 5GS services with control plane CIoT 5GSoptimization. In some embodiments, the UE can send a CONTROL PLANESERVICE REQUEST message, start T3517 and enter the state5GMM-SERVICE-REQUEST-INITIATED.

For the following cases, the UE may invoke the service request procedurewhen:

a) the UE, in 5GMM-IDLE mode over 3GPP access, receives a paging requestfrom the network;

b) the UE, in 5GMM-CONNECTED mode over 3GPP access, receives anotification from the network with access type indicating non-3GPPaccess;

c) the UE, in 5GMM-IDLE mode over 3GPP access, has uplink signallingpending;

d) the UE, in 5GMM-IDLE mode over 3GPP access, has uplink user datapending;

e) the UE, in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRCinactive indication, has user data pending due to no user-planeresources established for PDU session(s) used for user data transport;

f) the UE in 5GMM-IDLE mode over non-3GPP access, receives an indicationfrom the lower layers of non-3GPP access, that the access stratumconnection is established between UE and network;

g) the UE, in 5GMM-IDLE mode over 3GPP access, receives a notificationfrom the network with access type indicating 3GPP access when the UE isin 5GMM-CONNECTED mode over non-3GPP access;

h) the UE, in 5GMM-IDLE, 5GMM-CONNECTED mode over 3GPP access, or5GMM-CONNECTED mode with RRC inactive indication, receives a request foremergency services fallback from the upper layer and performs emergencyservices fallback; or

i) the UE, in 5GMM-CONNECTED mode over 3GPP access or in 5GMM-CONNECTEDmode with RRC inactive indication, receives a fallback indication fromthe lower layers and or the UE has a pending NAS procedure other than aregistration, service request, or de-registration procedure.

For case a, the Control plane service type of the CONTROL PLANE SERVICEREQUEST message shall indicate “mobile terminating request”. The UE mayinclude the ESM DATA TRANSPORT message. The UE shall not include any ESMmessage other than ESM DATA TRANSPORT message.

For case b, if the UE has pending IP or non-IP user data that is to besent via the control plane radio bearers, the Control plane service typeof the CONTROL PLANE SERVICE REQUEST message shall indicate “mobileoriginating request”. The UE shall include an ESM DATA TRANSPORT messagein the ESM message container IE. If the UE supports the CP-EDT, the UEshall provide the CONTROL PLANE SERVICE REQUEST message in the NASrequest to the lower layer to establish a RRC connection.

For cases b and m, if the UE has pending IP or non-IP user data that isto be sent via the user plane radio bearers, the UE shall set theControl plane service type of the CONTROL PLANE SERVICE REQUEST messageto “mobile originating request” and the “active” flag in the Controlplane service type IE to 1. The UE shall not include any ESM messagecontainer or NAS message container IE in the CONTROL PLANE SERVICEREQUEST message.

For case c, the UE shall set the Control plane service type of theCONTROL PLANE SERVICE REQUEST message to “mobile originating request”.If the CONTROL PLANE SERVICE REQUEST message is for sending SMS (shortmessage service) messages or any other similar message format accordingto any suitable messaging protocol, the UE shall include the SMS messageor the like in the NAS message container IE and shall not include anyESM message container IE in the CONTROL PLANE SERVICE REQUEST message.If the CONTROL PLANE SERVICE REQUEST message is for sending signalingdifferent from SMS messages, the UE shall not include any ESM messagecontainer or NAS message container IE in the CONTROL PLANE SERVICEREQUEST message.

In some embodiments, the service request procedure may be accepted bythe network when UE is using 5GS services with control plane CIoT 5GSoptimization. Referring back to case a, upon receipt of the CONTROLPLANE SERVICE REQUEST message with Control plane service type indicating“mobile terminating request”, after completion of the 5GMM commonprocedures, 1) if the AMF needs to initiate a PDU session statussynchronization for a PDU session associated with Control Plane onlyindication or for a PDU session not associated with Control Plane onlyindication, there is no downlink user data pending to be delivered viathe user plane, and the UE did not set the “active” flag in the ControlPlane service type IE to 1; or 2) if the control plane data back-offtime for the UE is stored in AMF and the AMF decides to deactivatecongestion control for transport of user data via the control plane,then the AMF shall send a SERVICE ACCEPT message.

Furthermore, the AMF may 1) initiate the transport of user data via thecontrol plane procedure or any other NAS signaling procedure; 2) ifsupported by the U and required by the network, initiate the setup ofthe user plan radio bearer(s); or 3) send a NAS signaling message notrelated to a 5GMM common procedure to the UE if downlink signaling ispending.

Referring back to case b, upon receipt of the CONTROL PLANE SERVICEREQUEST message with control plane service type indicating “mobileoriginating request,” after completion of the 5GMM common procedures, ifany, if the AMF needs to perform PDU session status synchronization forPDU session associated with control plane only indication or for PDUsession not associated with Control plane only indication, there is nodownlink user data pending to be delivered via the user plane, and theUE did not set the “active” flag in the Control plane service type IE to1, then the AMF shall send a SERVICE ACCEPT message.

Furthermore, the AMF may 1) initiate release of the NAS signallingconnection upon receipt of an indication from the ESM layer, unless theAMF has additional downlink user data or signalling pending; 2) initiatethe setup of the user plane radio bearer(s), if downlink user data ispending to be delivered via the user plane or the UE has set the“active” flag in the Control plane service type IE to 1; 3) send an ESMDATA TRANSPORT message to the UE, if downlink user data is pending to bedelivered via the control plane; 4) send a NAS signalling message notrelated to an 5GMM common procedure to the UE if downlink signalling ispending; or 5) send a SERVICE ACCEPT message to complete the servicerequest procedure, if no NAS security mode control procedure wasinitiated, the AMF did not send a SERVICE ACCEPT message as specifiedabove to perform PDU session status synchronization, and the AMF did notinitiate any of the procedures specified in item 1 to 4 above. In someembodiments, the AMF can initiate the setup of the user plane radiobearer(s) if the AMF decides to activate the congestion control fortransport of user data via the control plane.

Referring back to case m, upon receipt of the CONTROL PLANE SERVICEREQUEST message with Control plane service type indicating “mobileoriginating request” and the “active” flag in the Control plane servicetype IE set to 1, if the AMF accepts the request, the AMF shall initiatethe setup of the user plane radio bearer(s) for all active EPS bearercontexts of PDU sessions that are established without control plane onlyindication; if the AMF does not accept the request, the AMF shall send aSERVICE ACCEPT message to complete the service request procedure. Insome embodiments, the AMF can take into account the maximum number ofuser plane radio bearers supported by the UE, in addition to localpolicies and the UE's preferred CIoT network behaviour when decidingwhether to accept the request to establish user plane bearer(s). If theAMF accepts the request, all PDU sessions are considered as establishedwithout Control plane only indication. In some embodiments, a UE inNB-N1 mode can support a maximum number of user plane radio bearers(e.g., a maximum number of 2).

Referring back to case c, upon receipt of the CONTROL PLANE SERVICEREQUEST message with Control plane service type indicating “mobileoriginating request” and without an ESM message container IE, aftercompletion of the 5GMM common procedures, if any, the AMF proceeds asfollows: if the AMF needs to perform a PDU session statussynchronization for a PDU session associated with Control plane onlyindication; or for a PDU session not associated with Control plane onlyindication, and there is no downlink user data pending to be deliveredvia the user plane, then the AMF shall send a SERVICE ACCEPT message.

Furthermore, the AMF may 1) initiate the setup of the user plane radiobearer(s), if downlink user data is pending to be delivered via the userplane; 2) send an ESM DATA TRANSPORT message to the UE, if downlink userdata is pending to be delivered via the control plane; 3) send a NASsignalling message not related to an 5GMM common procedure to the UE, ifdownlink signalling is pending; or 4) send a SERVICE ACCEPT message tocomplete the service request procedure, if no NAS security mode controlprocedure was initiated, the AMF did not send a SERVICE ACCEPT messageas specified above to perform a PDU session status synchronization, andthe AMF did not initiate any of the procedures specified in item 1 to 3above.

In NB-N1 mode, for cases a, b, c and m, if the AMF needs to initiate thesetup of user plane radio bearer(s), the AMF shall check if the UE cansupport the establishment of additional user plane radio bearer based onthe multiple DRB support indicated by UE in the UE network capabilityIE.

For cases a, b and c, if the EPS bearer context status IE is included inthe CONTROL PLANE SERVICE REQUEST message, the network shall deactivateall those EPS bearer contexts locally (without peer-to-peer signallingbetween the network and the UE) which are active on the network side butare indicated by the UE as being inactive. If a default EPS bearercontext is marked as inactive in the EPS bearer context status IEincluded in the CONTROL PLANE SERVICE REQUEST message, and this defaultbearer is not associated with the last PDN connection of the UE in theAMF, the AMF shall locally deactivate all EPS bearer contexts associatedto the PDN connection with the default EPS bearer context withoutpeer-to-peer ESM signalling to the UE. If the default bearer isassociated with the last remaining PDN connection of the UE in the AMF,and 5GMM-REGISTERED without PDN connection is supported by the UE andthe AMF, the AMF shall locally deactivate all EPS bearer contextsassociated to the PDN connection with the default EPS bearer contextwithout peer-to-peer ESM signalling to the UE.

If the EPS bearer context status IE is included in the CONTROL PLANESERVICE REQUEST and the AMF decides to respond with a SERVICE ACCEPTmessage, the AMF shall include a PDU session status IE, indicating whichEPS bearer contexts are active in the AMF, except for the case when noEPS bearer context exists on the network side.

If the AMF needs to initiate PDU session status synchronization, the AMFmay include a PDU session status IE in the SERVICE ACCEPT message alsoif no EPS bearer context status IE was included in the CONTROL PLANESERVICE REQUEST message.

In an instance in which the AMF sends a SERVICE ACCEPT message uponreceipt of the CONTROL PLANE SERVICE REQUEST message piggybacked withthe ESM DATA TRANSPORT message, and if the Release assistance indicationIE is set to “No further uplink or downlink data transmission subsequentto the uplink data transmission is expected” in the message, if the UEhas indicated support for the control plane data back-off timer, or ifthe AMF decides to activate the congestion control for transport of userdata via the control plane, then the AMF shall include the T3448 valueIE in the SERVICE ACCEPT message.

If the AMF sends a SERVICE ACCEPT message and decides to deactivatecongestion control for transport of user data via the control plane thenthe AMF shall delete the stored control plane data back-off time for theUE and the AMF shall not include timer T3448 value IE in SERVICE ACCEPTmessage.

For cases a, b, c, and m, if the EPS bearer context status IE isincluded in the CONTROL PLANE SERVICE REQUEST message or the AMF needsto initiate PDU session status synchronization, the AMF shall considerthe service request procedure successfully completed when it sends theSERVICE ACCEPT message. If the EPS bearer context status IE is notincluded in the CONTROL PLANE SERVICE REQUEST message and the AMF doesnot need to initiate PDU session status synchronization, the AMF shallconsider the service request procedure successfully completed in thefollowing cases:

-   -   when it successfully completes a NAS security mode control        procedure;    -   when it receives an indication from the lower layer that the        user plane is setup, if radio bearer establishment is required;    -   upon receipt of the CONTROL PLANE SERVICE REQUEST message and        completion of the 5GMM common procedures, if any, if the CONTROL        PLANE SERVICE REQUEST message was successfully integrity checked        and the ESM message container or NAS message container in the        CONTROL PLANE SERVICE REQUEST message, if applicable, was        successfully deciphered, radio bearer establishment is not        required, and the AMF has downlink user data or signalling not        related to an 5GMM common procedure pending; and    -   with the transmission of a SERVICE ACCEPT message or with the        decision to initiate release of the NAS signalling connection,        if the CONTROL PLANE SERVICE REQUEST message was successfully        integrity checked and the ESM message container or NAS message        container in the CONTROL PLANE SERVICE REQUEST message, if        applicable, was successfully deciphered, radio bearer        establishment is not required, and the AMF does not have any        downlink user data or signalling pending.

If the AMF considers the service request procedure successfullycompleted the AMF shall: 1) forward the contents of the ESM messagecontainer IE, if any, to the ESM layer; and 2) forward the contents ofthe NAS message container IE, if any.

For cases a, b, and c, the UE shall treat the receipt of any of thefollowing as successful completion of the procedure:

-   -   a SECURITY MODE COMMAND message;    -   a security protected 5GMM message different from a SERVICE        REJECT message and not related to an 5GMM common procedure;    -   a security protected ESM message; and    -   receipt of the indication from the lower layers that the user        plane radio bearers are set up.

Upon successful completion of the procedure, the UE shall reset theservice request attempt counter, stop the timer T3417 and enter thestate 5GMM-REGISTERED.

In some embodiments, the security protected 5GMM message can be e.g. aSERVICE ACCEPT message and the ESM message an ESM DATA TRANSPORTmessage.

For case m, the UE shall treat the indication from the lower layers thatthe user plane radio bearers are set up as successful completion of theprocedure. The UE shall treat the receipt of a SERVICE ACCEPT message ascompletion of the procedure without the establishment of the user planeradio bearers. For both cases, the UE shall reset the service requestattempt counter, stop the timer T3417 and enter the state5GMM-REGISTERED.

For case b, the UE shall also treat the indication from the lower layersthat the RRC connection has been released as successful completion ofthe procedure. The UE shall reset the service request attempt counter,stop the timer T3417 and enter the state 5GMM-REGISTERED.

For cases a, c, and m, the UE shall treat the indication from the lowerlayers that the RRC connection has been released as an abnormal case.

For cases a, b, and c, if the AMF needs to initiate PDU session statussynchronization, the UE can receive a SERVICE ACCEPT message even afterit received a SECURITY MODE COMMAND message or an indication from thelower layers that the user plane radio bearers are set up and determinedsuccessful completion of the service request procedure. Upon receipt ofthe SECURITY MODE COMMAND message or an indication from the lower layersthat the user plane radio bearers are set up, the UE shall start timerT3449. If the UE receives a security protected ESM message or a securityprotected 5GMM message not related to a 5GMM common procedure, the UEshall stop the timer T3449. If the UE receives a SERVICE ACCEPT messagewhile the timer T3449 is running, the UE shall treat the SERVICE ACCEPTmessage and stop the timer T3449. If the UE is not in state5GMM-SERVICE-REQUEST-INITIATED and timer T3449 is not running, thereceipt of the SERVICE ACCEPT message is considered as protocol errorand the UE shall return 5GMM STATUS message; otherwise the UE shalltreat the SERVICE ACCEPT message; and if the UE treats the SERVICEACCEPT message and PDU session status IE is included in the message, theUE shall deactivate all those EPS bearers contexts locally (withoutpeer-to-peer signalling between the UE and the AMF) which are active inthe UE, but are indicated by the AMF as being inactive. If a default EPSbearer context is marked as inactive in the EPS bearer context status IEincluded in the SERVICE ACCEPT message, and this default bearer is notassociated with the last remaining PDN connection in the UE, the UEshall locally deactivate all EPS bearer contexts associated to the PDNconnection with the default EPS bearer context without peer-to-peer ESMsignalling to the AMF. If the default bearer is associated with the lastremaining PDN connection of the UE in the AMF, and 5GMM-REGISTEREDwithout PDN connection is supported by the UE and the AMF, the UE shalllocally deactivate all EPS bearer contexts associated to the PDNconnection with the default EPS bearer context without peer-to-peer ESMsignalling to the AMF.

If the T3448 value IE is present in the received SERVICE ACCEPT message,the UE shall stop timer T3448 if it is running, consider the transportof user data via the control plane as successful, and start timer T3448with the value provided in the T3448 value IE.

If the UE is using EPS services with control plane CIoT EPSoptimization, the T3448 value IE is present in the SERVICE ACCEPTmessage and the value indicates that this timer is either zero ordeactivated, the UE shall consider this case as an abnormal case andproceed as if the T3448 value IE is not present.

If the UE in 5GMM-IDLE mode initiated the service request procedure bysending a CONTROL PLANE SERVICE REQUEST message and the SERVICE ACCEPTmessage does not include the T3448 value IE and if timer T3448 isrunning, then the UE shall stop timer T3448.

Referring now to FIG. 5, a network-initiated NAS transport process fordownlink user data delivery via control plane over N6 interface in a 5Gsystem is illustrated. In some embodiments, the network-initiated NAStransport procedure can be used to provide a transport of CIoT user dataover control plane from the AMF to the UE in a 5GMM message. In someembodiments, the process includes a UE registering with the AMF for CIoTcontrol plane optimizations (CP-CIoT). The process can further includeestablishment of a NAS Security Context at both the UE and AMF andciphering and integrity protection at both the UE and AMF. The processcan further include the establishment of an association (association)between the AMF and an SMF. The process can further include theassociation of the SMF with a UPF PFCP (UPF). The process can furtherinclude the transmission of a PFCP_data_forwarding (N3-u tunnerl ID,payload_container [user data]) message from the UPF to the SMF. Theprocess can further include the transmission of anNsmf_PDUSession_DataTransfer Notify (payload_container [user data], PDUsession ID) message from the SMF to the AMF. The process can furtherinclude the transmission or transport or downlink NAS transport data (orthe establishment of a downlink NAS transport pathway) (e.g., ngKSI,payload_container_type=“CIoT user data container”, payload_container[user data, PDU session ID]) from or between the AMF and the UE.

In some embodiments, in 5GMM-CONNECTION mode, the AMF initiates the NAStransport procedure by sending the DL NAS TRANSPORT message. In someembodiments, upon reception from an SMF of a 5GSM message indicatinguser data for a UE in the 5GMM-CONNECTION mode, the AMF can include thePDU session information (PDU session ID) in the PDU session ID IE, andset the Payload container type IE to “CIoT user data container”, and setthe Payload container IE to the 5GSM message. In some embodiments, uponreception of a DL NAS TRANSPORT message, the UE can or shall stop thetimer T3346, if running. In some embodiments, if the Payload containertype IE is set to “CIoT user data transfer” and if the Payload containerIE successfully passes the integrity check and the 5GSM message in thePayload container IE and the PDU session ID is valid; the UE can orshall forward the CIoT user data to an upper layer (e.g., AMF, SMF, UPF,or the like).

In some embodiments, the SERVICE REQUEST message, such as a ControlPlane Service Request Message, can be defined according to the messagetype, significance, direction, presence, format, length, and/or thelike. In some embodiments, the SERVICE REQUEST message can be sent bythe UE to the AMF in order to request transport of user data via thecontrol plane. Therefore, in some embodiments, a message can have a typeof CONTROL PLANE SERVICE REQUEST, a significance of DUAL, and adirection of UE to network. Table 1 identifies some example informationelements for CONTROL PLANE SERVICE REQUEST message content.

TABLE 1 CONTROL PLANE SERVICE REQUEST message content IEI InformationElement Type (Reference) Presence Format Length Extended protocolExtended protocol M V 1 discriminator discriminator (9.2) Securityheader type Security header type (9.3) M V 1/2 Spare half octet Sparehalf octet (9.5) M V 1/2 Control plane Message type (9.7) M V 1 servicerequest message identity ngKSI NAS key set identifier M V 1/2(9.11.3.32) xx Payload container type Payload container type 0 TV 1/2(9.11.3.40) yy Payload container Payload container 0 TLV-E 3-65537(9.11.3.39) 50 PDU session status PDU session status 0 TLV 4-34(9.11.3.44) 25 Allowed PDU Allowed PDU session status 0 TLV 4-34 sessionstatus (9.11.3.13) 71 NAS message NAS message container 0 TLV-E 4-ncontainer (9.11.3.33)

In some embodiments payload container type can be included if the UEincludes the Payload container IE. In some embodiments, the Payloadcontainer IE can be included if the UE has one or more data packets tobe transferred. In some embodiments, the PDU Session Status IE can beincluded when the UE needs to indicate the PDU sessions that areassociated with the access type that the message is sent over, that areactive within the UE. In some embodiments, the Allowed PDU SessionStatus IE can be included if the SERVICE REQUEST message is sent inresponse to paging or notification via 3GPP access for PDU session(s)associated with non-3GPP access and the UE needs to indicate theuser-plane resources of PDU session(s) associated with non-3GPP accessallowed to be re-established over 3GPP access or if there is no PDUsession(s) for which the UE allows the user-plane resources to bere-established over 3GPP access. In some embodiments the NAS MessageContainer IE can be included if the UE is sending a SERVICE REQUESTmessage as an initial NAS message and the UE needs to send non-cleartextIEs.

In some embodiments, the purpose of the Payload container informationelement is to transport one or multiple payloads. If multiple payloadsare transported, the associated information of each payload are alsotransported together with the payload. In some embodiments, the Payloadcontainer information element is coded as shown in in FIG. 6. In someembodiments, the Payload container IE can be a type 6 informationelement with a minimum length of 4 octets and a maximum length of 65538octets.

As such, in some embodiments, the Payload container contents (octed 4 tooctet n) may have a max value of 65535 octets. In some embodiments, ifthe payload container type is set to “CIoT user data container” and isincluded in the CONTROL PLANE SERVICE REQUEST message, the payloadcontainer contents are coded the same way as the contents of the userdata container IE for UE parameters update data type is set to value “0”except that the first three octets are not included. In someembodiments, the coding of Payload container contents is dependent onthe particular application. In some embodiments, if the payloadcontainer type is set to “CIoT user data container” and is included inthe DL NAS TRANSPORT message, the payload container contents can becoded the same way as the contents of the user data container IE exceptthat the first three octets are not included.

In some embodiments, a new payload container type “CIoT user datacontainer” can be used, as illustrated in FIG. 7. In some embodiments,the purpose of the Payload container type information element can be toindicate the type of payload included in the payload containerinformation element. In some embodiments, for example, the Payloadcontainer type value (octet 1) can have bits of “4, 3, 2, 1 . . . 0, 0,0, 1” where the “0, 0, 0, 1” refers to the CIoT user data container.

In some embodiments, when a DL NAS TRANSPORT message is used totransport CIoT user data from the AMF to the UE, the payload containertype can be set to “CIoT user data container” and the user data can beincluded in Payload container IE, such as indicated in Table 2.

TABLE 2 DL NAS TRANSPORT message content IEI Information ElementType/Reference Presence Format Length ... DL NAS TRANSPORT Message typeM V 1 message identity 9.7 Payload container type Payload container typeM V 1/2 9.11.3.40 Spare half octet Spare half octet M V 1/2 9.5 Payloadcontainer Payload container M LV-E 3-65537 9.11.3.39 ....

According to an alternative embodiments, a control plane service requestprocedure enables the UE to change from 5GMM-IDLE to 5GMM-CONNECTEDmode. If the UE is using 5GS services with control plant CIoT 5GSOptimization, this procedure can be used for user equipment transfer ofuser data via the control plane. For instance, the control plane servicerequest procedure can be used for transport uplink or downlink user dataor SMS messages via the control plane for the UE in 5GMM-IDLE mode.

In some embodiments, the UE, when operating in IDLE mode over 3GPPaccess, can have user data uplink and SMS messages pending, can havedownlink user data or SMS messages pending (may receive a paging requestfrom the network), and/or can have uplink signaling pending. In someembodiments, user equipment operating in IDLE mode over 3GPP access canhave uplink user data pending while the UE also uses 5GS services withcontrol plane CIoT 5GS optimization.

Referring now to FIG. 8, a process for uplink transfer of single userdata via control plane to a data network over N6 interface for userequipment in IDLE mode is illustrated. The process of FIG. 8 or anyportion thereof can be carried out by any suitable computing device,such as the apparatus of FIG. 1, and in particular one or moreprocessors in conjunction with computer program instructions stored onone or more memory devices. As illustrated, the process can include theregistration of user equipment with an AMF for CIoT control planeoptimizations. The UE and the AMF then both carry out a security setupvia the NAS security context and carry out a ciphering and integrityprotection procedure. The UE is then in IDLE mode. The UE, whileremaining in IDLE mode, sends a control plane service request, such as acontrol plane service type “mobile originating request”,payload_container name, “CIoT user data container”, payload_container[user data], PDU session ID, PDU session status, and/or ReleaseAssistance Info, to the AMF. In some embodiments, the AMF can thenforward the user data to the SMF associated with the UE, for instance asa Nsmf_PDUSession_DataTransfer Request (user data, PDU session ID). Ator about the same time the AMF can send a Service Accept (PDU SessionStatus) message back to the UE. The UE can then switch in from IDLE modeto CONNECTED mode. At or about the same time, the SMF can then select aUPF or NEF for user data delivery based on configuration. A RadioResource Control (RRC) connection can then be established between the UEand the AMF. The SMF can then send a PFCP_data_forwarding (N4-u tunnerlID, payload_container [user data]) message or the like to the UPF or NEFselected. At or about the same time, the AMF can then release the RRCconnection based on the Release Assistance information.

Referring now to FIG. 9, a process for uplink transfer of multipleuser's user data and SMS messages via control plane for user equipmentin IDLE mode is illustrated. The process of FIG. 9 or any portionthereof can be carried out by any suitable computing device, such as theapparatus of FIG. 1, and in particular one or more processors inconjunction with computer program instructions stored on one or morememory devices. As illustrated, the process can include the registrationof user equipment with an AMF for CIoT control plane optimizations. TheUE and the AMF then both carry out a security setup via the NAS securitycontext and carry out a ciphering and integrity protection procedure.The UE is then in IDLE mode. The UE, while remaining in IDLE mode, sendsa control plane service request, such as a control plane service type“mobile originating request”, payload_container_type=“multiplepayloads”, payload_container [payload entry1 (type=“CIoT user datacontainer”, user data, PDU Session ID, PDU Session Status, ReleaseAssistance Info, payload entry2 (type=“CIoT user data container”, SMS) .. . ]) and/or the like, to the AMF. The AMF can forward the user data tothe SMF and the SMS Function (SMSF) associated with the UE. Forinstance, the AMF can send a Nsmf_PDUSession_DataTransfer request (username, PDU session ID) to the SMF and a Nsmsf_SMService_ForwardSMRequest(SMS message) to the SMSF. The AMF can then send a Service Accept (PDUSession Status) message back to the UE. The UE can then switch from IDLEmode into CONNECTED mode. The SMF, at or about the same time, can thenselect a UPF or NEF for user data delivery based on configuration. AnRRC connection can then be established between the UE and the AMF. TheAMF can then release the RRC connection based on Release Assistanceinformation.

In some embodiments, a process for uplink user data transfer via controlplane for UE in IDLE mode can be carried out when a SMS message is sentor multiple uplink user data is to be sent. In some embodiments, if theUE has uplink user data to be sent, the UE sets the Control planeservice type of the CONTROL PLANE SERVICE REQUEST message to “mobileoriginating request”. In some embodiments, the UE shall set the Payloadcontainer type IE to “CIoT user data container” and set the Payloadcontainer IE to the user data container. In some embodiments, the UE caninclude with such a request the PDU session information (PDU session ID,PDU session status) associated with user data to be sent in the PDUsession ID IE. In some embodiments, if the UE has additionally SMSmessages to be sent or multiple uplink user data to be sent, the UEshall set the Payload container type IE to “multiple payload” andinclude SMS message and uplink user data in the payload_container asindividual payload entry to be included in the payload_container IE. Foreach user data entry, the Payload container type IE of the payload entryis set to “CIoT user data container”. For SMS message entry, the Payloadcontainer type IE of the payload entry is set to “SMS”. In someembodiments, the UE can send a CONTROL PLANE SERVICE REQUEST message,start T3517 (a timer) and enter the state5GMM-SERVICE-REQUEST-INITIATED. In some embodiments, upon receipt of theCONTROL PLANE SERVICE REQUEST message with Control plane service typeindicating “mobile originating request”, after completion of the 5GMMcommon procedures, the AMF shall send a SERVICE ACCEPT message to theUE. In some embodiments, if the Payload container IE is included in theCONTROL PLANE SERVICE REQUEST message, if the Payload container type IEis set to “CIoT user data container” and if the Payload container IEsuccessfully passes the integrity check and the PDU session ID is valid,the AMF forwards the content of the Payload container IE to the SMFassociated with the UE. In some embodiments, and if the Payloadcontainer IE is included in the CONTROL PLANE SERVICE REQUEST message,if the Payload container type IE is set to “SMS”, the AMF forwards thecontent of the Payload container IE to the SMSF associated with the UE.In some embodiments, if the Payload container IE is included in theCONTROL PLANE SERVICE REQUEST message, and if the Payload container typeIE is set to “multiple payload”, the AMF extracts each payload entry andhandle in a similar manner based on whether the entry type is “CIoT userdata container” or “SMS”. In some embodiments, if the PDU session statusIE is included in the message or the AMF needs to perform a PDU sessionstatus synchronization, the AMF shall include a PDU session status IE inthe SERVICE ACCEPT message to indicate which PDU sessions associatedwith the access type the SERVICE ACCEPT message is sent over are activein the AMF. In some embodiments, upon successful completion of theprocedure, the UE shall reset the service request attempt counter, stopthe timer T3517 and enter the state 5GMM-REGISTERED. In someembodiments, the UE shall also treat the indication from the lowerlayers that the RRC connection has been released as successfulcompletion of the procedure. In some embodiments, if the PDU sessionstatus information element is included in the SERVICE ACCEPT message,then the UE shall perform a local release of all those PDU sessionswhich are active on the UE side associated with the 3GPP access but areindicated by the AMF as being inactive.

Referring now to FIG. 10, a process is illustrated for user equipment inIDLE mode over 3GPP access to have downlink user data pending while theUE is using 5GS services with control plane CIoT 5GS optimization. Theprocess of FIG. 10 or any portion thereof can be carried out by anysuitable computing device, such as the apparatus of FIG. 1, and inparticular one or more processors in conjunction with computer programinstructions stored on one or more memory devices. As illustrated, theprocess can include the downlink transfer of multiple user's user dataor a combination of SMS message(s) and user data via control plane foruser equipment in IDLE mode. As illustrated, the process can include theregistration of user equipment with an AMF for CIoT control planeoptimizations, for example via an NG-RAN. The UE and the AMF then bothcarry out a security setup via the NAS security context and carry out aciphering and integrity protection procedure. The UE is then in IDLEmode. In some embodiments, the approach can subsequently includeestablishment of an AMF/SMF Association and subsequently includeestablishment of an SMF/UPF PFCP Association. A message is thentransmitted from the UPF to the SMF and from the SMF to the AMF totransmit a Nsmf_PDUSession_DataTransfer Notify (user data, PDU sessionID) message. The AMF then pages the UE regarding the downlink transferand the UE transmits a Control Plane Service Request (control planeservice type=“mobile terminating request”, payload_container_type=“CIoTuser data container”, payload_container [user data], PDU session ID,and/or Release Assistance Info) to the AMF. The AMF then sends a ServiceAccept (PDU session status) message back to the UE and the UEsubsequently switches from IDLE mode to CONNECTED mode. The AMF can thensend a DL NAS transport (payload_container_type=“CIoT user datacontainer”, payload_container [user data], PDU session ID) message tothe UE.

Referring now to FIG. 11, a process for downlink transfer of multipleuser's user data and SMS messages via control plane for user equipmentin IDLE mode is illustrated. The process of FIG. 11 or any portionthereof can be carried out by any suitable computing device, such as theapparatus of FIG. 1, and in particular one or more processors inconjunction with computer program instructions stored on one or morememory devices. As illustrated, the process can include the downlinktransfer of multiple user's user data or a combination of SMS message(s)and user data via control plane for user equipment in IDLE mode. Asillustrated, the process can include the registration of user equipmentwith an AMF for CIoT control plane optimizations, for example via anNG-RAN. The UE and the AMF then both carry out a security setup via theNAS security context and carry out a ciphering and integrity protectionprocedure. The UE is then in IDLE mode. In some embodiments, theapproach can subsequently include establishment of an AMF/SMFAssociation and subsequently include establishment of an SMF/UPF PFCPAssociation. The process can further include transmission of aPFCP_data_forwarding (N4-u tunnerl ID, payload_container [user data])message from the UPF to the SMF. The process can further includetransmission of a Nsmf_PDUSession_DataTransfer Notify (user data, PDUSession ID) message from the SMF to the AMF. The AMF then pages the UEthat the AMF is ready to receive service requests. The UE then sends aControl Plane Service Request (control plane service type=“mobileterminating request”, payload_container_type=“multiple payloads”,payload_container [payload entry 1 (type=“CIoT user data container”,user data, PDU Session ID, PDU Session status, Release Assistanceinfo_payload entry2 (type=“CIoT user data container”, SMS) . . . ]) tothe AMF. The AMF then sends a Service Accept (PDU session status)message to the UE and the UE then switches from IDLE mode to CONNECTEDmode. The AMF then transmits a DL NAS Transport(payload_container_type=“CIoT user data container”, payload_container[user data], PDU Session ID) message to the UE.

In some embodiments, a process for downlink user data transfer formultiple user's user data and SMS messages via control plane for userequipment in IDLE mode can be carried out. In some embodiments, theprocess can comprise an AMF receiving downlink user data from a SMF andinitiate paging of the UE. In some embodiments, upon receiving pagingfrom AMF, the UE can initiate a Control plane service request. In someembodiments, the Control plane service type of the CONTROL PLANE SERVICEREQUEST message indicates “mobile terminating request”. Additionally, insome embodiments, if the UE has uplink user data to be sent, the UEshall set the Payload container type IE to “CIoT user data container”and set the Payload container IE to the user data container. In someembodiments, the UE can include the PDU session information (PDU sessionID, PDU session status) associated with user data to be sent in the PDUsession ID IE. In some embodiments, if the UE has uplink SMS messages tobe sent, the UE shall set the Payload container type IE to “SMS” andinclude the SMS message in the Payload container IE. In someembodiments, if the UE has both uplink user data and SMS messages to besent, the UE shall set the Payload container type IE to “multiplepayload” and include SMS message and uplink user data in the payloadcontainer as individual payload entry according to any of the approachesdescribed herein. In some embodiments, if the UE has multiple uplinkuser data or multiple SMS messages to be sent, each can be included asindividual payload entry in the payload container IE. IN someembodiments, the process can comprise the UE sending the CONTROL PLANESERVICE REQUEST message to the AMF, start T3517 (a timer) and enter thestate 5GMM-SERVICE-REQUEST-INITIATED. In some embodiments, upon receiptof the CONTROL PLANE SERVICE REQUEST message with Control plane servicetype indicating “mobile originating request”, after completion of the5GMM common procedures, the AMF shall send a SERVICE ACCEPT message tothe UE. In some embodiments, if the Payload container IE is included inthe CONTROL PLANE SERVICE REQUEST message and if the Payload containertype IE is set to “CIoT user data container”, the AMF forwards thecontent of the Payload container IE to the SMF associated with the UE.In some embodiments, if the Payload container type IE is set to “SMS”,the AMF forwards the content of the Payload container IE to the SMSFassociated with the UE. In some embodiments, if the Payload containertype IE is set to “multiple payload”, the AMF extracts each payloadentry and handle according to any of the approaches described hereinbased on whether the entry type is “CIoT user data container” or “SMS”.In some embodiments, if the PDU session status IE is included in themessage or the AMF needs to perform a PDU session statussynchronization, the AMF shall include a PDU session status IE in theSERVICE ACCEPT message to indicate which PDU sessions associated withthe access type the SERVICE ACCEPT message is sent over are active inthe AMF. In some embodiments, the process can continue upon successfulcompletion of the procedure, when the UE shall reset the service requestattempt counter, stop the timer T3517 and enter the state5GMM-REGISTERED. The UE shall also treat the indication from the lowerlayers that the RRC connection has been released as successfulcompletion of the procedure. In some embodiments, if the PDU sessionstatus information element is included in the SERVICE ACCEPT message,then the UE shall perform a local release of all those PDU sessionswhich are active on the UE side associated with the 3GPP access but areindicated by the AMF as being inactive. In some embodiments, the AMF caninclude downlink user data using DL NAS TRANSPORT message by setting thePayload container type IE to “CIoT user data container” and set thePayload container IE to the user data container. In some embodiments, ifthere are also downlink SMS messages to be sent, the AMF sets thePayload container type IE to “multiple payload” and include a SMSmessage and downlink user data in the payload container as separatepayload entry, with each entry formatted to include Payload containertype to indicate the payload for each entry (same as when sentindividually). In some embodiments, upon receipt of the DL NAS TRANSPORTmessage if the Payload container IE is included, if the Payloadcontainer type IE is set to “CIoT user data container” and if thePayload container IE successfully passes the integrity check and the PDUsession ID is valid, the UE can forward the content of the Payloadcontainer IE to the upper layer. In some embodiments, upon receipt ofthe DL NAS TRANSPORT message if the Payload container IE is included, ifthe Payload container type IE is set to “SMS”, the UE can forward thecontent of the Payload container IE to the SMS message stack entity. Insome embodiments, upon receipt of the DL NAS TRANSPORT message if thePayload container IE is included, if the Payload container type IE isset to “multiple payload”, the UE can extract each payload entry andhandle according to any of the approaches described herein based onwhether the entry type is “CIoT user data container” or “SMS”.

Referring now to FIG. 12, CIoT user data can be delivered via controlplane for user equipment in CONNECTED mode. FIG. 12 illustrates aprocess for uplink transfer of user equipment single user data viacontrol plane to a data network over N6 interface for user equipment inCONNECTED mode. The process of FIG. 12 or any portion thereof can becarried out by any suitable computing device, such as the apparatus ofFIG. 1, and in particular one or more processors in conjunction withcomputer program instructions stored on one or more memory devices. Asillustrated, the process can include the registration of user equipmentwith an AMF for CIoT control plane optimizations, for example via anNG-RAN. The UE and the AMF then both carry out a security setup via theNAS security context and carry out a ciphering and integrity protectionprocedure. The UE is then in CONNECTED mode. In some embodiments, theapproach can subsequently include the UE transmitting a UL_NAS_TRANSPORT(payload_container_type=“CIoT user data container”, payload_container[user data], PDU session ID, PDU session status, Release Assistanceinfo) message to the AMF. The AMF can then forward user data to the SMFassociated with the UE. The AMF can transmit aNsmf_PDUSession_DataTransfer Request (user data, PDU session ID) messageto the SMF. The SMF can then select a UPF or NEF for user data deliverybased on configuration and transmit a PFCP_data_forwarding (N4-u tunnerlID, payload_container [user data]) message to the UPF. The AMF can thenrelease an RRC connection based on the Release Assistance informationand transmit possible downlink data to the UE. An RRC connection can bereleased between the UE and the AMF and the UE can switch from CONNECTEDmode to IDLE mode.

Referring now to FIG. 13, a process for uplink transfer of multiple userdata or combination of SMS message(s) and user data via control planefor user equipment in CONNECTED mode is illustrated. The process of FIG.13 or any portion thereof can be carried out by any suitable computingdevice, such as the apparatus of FIG. 1, and in particular one or moreprocessors in conjunction with computer program instructions stored onone or more memory devices. As illustrated, the process can include theregistration of user equipment with an AMF for CIoT control planeoptimizations, for example via an NG-RAN. The UE and the AMF then bothcarry out a security setup via the NAS security context and carry out aciphering and integrity protection procedure. The UE is then inCONNECTED mode. In some embodiments, the approach can subsequentlyinclude transmission of a UL_NAS_TRANSPORT(payload_container_type=“multiple payloads”, payload_container [payloadentry 1 (type=“CIoT user data container”, user data, PDU session ID, PDUsession status, Release Assistance info), payload entry2 (type=“CIoTuser data container”, SMS) . . . ]) message from the UE to the AMF. TheAMF can forward the user data to the SMF associated with the UE andtransmit a Nsmf_PDUSession_DataTransfer Request (user data, PDU sessionID) and send a Nsmsf_SMService_ForwardSMRequest (SMS message) to theSMSF. The SMF can then select a UPF or NEF for user data delivery basedon configuration and sent a PFCP_data_forwarding (N4-u tunnerl ID,payload_container [user data]) message to the UPF or NEF. At or aboutthe same time, the AMF can release the RRC connection based on theRelease Assistance information and transit the possible downlink data tothe UE. The RRC connection between the UE and the AMF can then bereleased. The UE can then switch from CONNECTED mode to IDLE mode.

In some embodiments, a process for uplink transfer of multiple user'suser data via control plane for user equipment in CONNECTED mode can becarried out as follows. In particular, if the UE has uplink user data tobe sent, the UE can set the Payload container type IE to “CIoT user datacontainer” and set the Payload container IE to the user data container.The UE can include the PDU session information (PDU session ID, PDUsession status) associated with user data to be sent in the PDU sessionID IE. In some embodiments, if the UE additionally has a SMS message tobe sent or multiple user's uplink user data to be sent, the UE shall setthe Payload container type IE to “multiple payload” and include the SMSmessage(s) and uplink user data in the payload container as individualpayload entry to be included in the payload container IE. For each userdata entry, the Payload container type IE of the payload entry is set to“CIoT user data container”. For SMS message entry, the Payload containertype IE of the payload entry is set to “SMS”. In some embodiments, theUE can include the Payload container type and the Payload container,formatted as above, in a UL NAS DATA TRANSPORT message, and sends themessage to the AMF. In some embodiments, upon receipt of the UL NAS DATATRANSPORT message, if the Payload container IE is included in the UL NASDATA TRANSPORT message, if the Payload container type IE is set to “CIoTuser data container” and if the Payload container IE successfully passesthe integrity check and the PDU session ID is valid, the AMF forwardsthe content of the Payload container IE to the SMF associated with theUE. In some embodiments, upon receipt of the UL NAS DATA TRANSPORTmessage, if the Payload container IE is included in the UL NAS DATATRANSPORT message, if the Payload container type IE is set to “SMS”, theAMF forwards the content of the Payload container IE to the SMSFassociated with the UE. In some embodiments, upon receipt of the UL NASDATA TRANSPORT message, if the Payload container IE is included in theUL NAS DATA TRANSPORT message, if the Payload container type IE is setto “multiple payload”, the AMF extracts each payload entry and handlethe same way as described above based on whether the entry type is “CIoTuser data container” or “SMS”.

Referring now to FIG. 14, a process is described for downlink user datadelivery over control plane for user equipment in CONNECTED mode. Foruser equipment in CONNECTED mode, a network-initiated NAS transportprocedure can be used to provide a transport of CIoT user data overcontrol plane from the AMF to the UE in a 5GMM message. For instance,illustrated in FIG. 14 is a process for the downlink transfer of singleuser data via control plane to a data network over N6 interface in a 5Gsystem. The process of FIG. 14 or any portion thereof can be carried outby any suitable computing device, such as the apparatus of FIG. 1, andin particular one or more processors in conjunction with computerprogram instructions stored on one or more memory devices. Asillustrated, the process can include the registration of user equipmentwith an AMF for CIoT control plane optimizations, for example via anNG-RAN. The UE and the AMF then both carry out a security setup via theNAS security context and carry out a ciphering and integrity protectionprocedure. The UE is then in CONNECTED mode. In some embodiments, anAMF/SMF Association can be established between the AMF and the SMFchosen for the UE. In some embodiments a SMF/UPF PFCP Association can beestablished between the SMF and the UPF. In some embodiments, a messagerelated to the downlink transfer can be transmitted from the UPF to theSMF and from the SMF to the AMF. In some embodiments, a message from atleast the SMF to the AMF can comprise a Nsmf_PDUSession_DataTransferNotify (payload_container [user data], PDU session ID) message. In someembodiments, the downlink NAS transport (payload_container_type=“CIoTuser data container”, payload_container [user data], PDU session ID) canbe transmitted between the AMF and the UE.

Referring now to FIG. 15, a process is illustrated for the downlinktransfer of multiple user data or combination of SMS message(s) and userdata via control plane for user equipment in CONNECTED mode. For userequipment in CONNECTED mode, a network-initiated NAS transport procedurecan be used to provide a transport of CIoT user data over control planefrom the AMF to the UE in a 5GMM message. The process of FIG. 15 or anyportion thereof can be carried out by any suitable computing device,such as the apparatus of FIG. 1, and in particular one or moreprocessors in conjunction with computer program instructions stored onone or more memory devices. As illustrated, the process can include theregistration of user equipment with an AMF for CIoT control planeoptimizations, for example via an NG-RAN. The UE and the AMF then bothcarry out a security setup via the NAS security context and carry out aciphering and integrity protection procedure. The UE is then inCONNECTED mode. In some embodiments, an AMF/SMF Association can beestablished between the AMF and the SMF chosen for the UE. In someembodiments a SMF/UPF PFCP Association can be established between theSMF and the UPF. In some embodiments, the UPF can transmit aPFCP_data_forwarding (N4-u tunnerl ID, payload_container [user data])message to the SMF. The SMF can then transmit anNsmf_PDUSession_DataTransfer Notify (payload_container [user data], PDUsession ID) message to the AMF. The AMF can then transmit the downlinkNAS transport (payload_container_type=“multiple payloads”,payload_container [payload entry 1 type=“CIoT user data container”, userdata, PDU session ID, PDU session status, Release Assistance info),payload entry2 (type=“CIoT user data container”, SMS) . . . ]) messageto the UE.

A process for downlink user data transfer via control plane for userequipment in CONNECTED mode can be carried out in a 5GMM message system.For example, if the AMF has downlink user data to be sent, the AMF canset the Payload container type IE to “CIoT user data container” and setthe Payload container IE to the user data container. The UE can includethe PDU session information (PDU session ID, PDU session status)associated with user data to be sent in the PDU session ID IE. In someembodiments, if the AMF has additionally SMS messages to be sent ormultiple downlink user data to be sent to the UE, the AMF shall set thePayload container type IE to “multiple payload” and include SMS messagesand uplink user data in the payload container as individual payloadentry in the payload_container IE. For each user data entry, the Payloadcontainer type IE of the payload entry is set to “CIoT user datacontainer”. For SMS message entry, the Payload container type IE of thepayload entry is set to “SMS”. In some embodiments, the AMF can includePayload container type and Payload container formatted as above in a DLNAS DATA TRANSPORT message, and send the message to the UE. In someembodiments, upon receipt of the DL NAS TRANSPORT message, if thePayload container IE is included in the CONTROL PLANE SERVICE REQUESTmessage, and if the Payload container type IE is set to “CIoT user datacontainer” and if the Payload container IE successfully passes theintegrity check and the PDU session ID is valid, the UE forwards thecontent of the Payload container IE to the upper layer. In someembodiments, upon receipt of the DL NAS TRANSPORT message, if thePayload container IE is included in the CONTROL PLANE SERVICE REQUESTmessage, and if the Payload container type IE is set to “SMS”, the UEforwards the content of the Payload container IE to the SMS messagestack entity. In some embodiments, upon receipt of the DL NAS TRANSPORTmessage, if the Payload container IE is included in the CONTROL PLANESERVICE REQUEST message, and if the Payload container type IE is set to“multiple payload”, the UE extracts each payload entry and handles thesame way as described above based on whether the entry type is “CIoTuser data container” or “SMS”.

Referring now to FIG. 16, a process for the uplink transfer of an SMSmessage via control plane for user devices in IDLE mode. The process ofFIG. 16 or any portion thereof can be carried out by any suitablecomputing device, such as the apparatus of FIG. 1, and in particular oneor more processors in conjunction with computer program instructionsstored on one or more memory devices. As illustrated, the process caninclude the registration of user equipment with an AMF for CIoT controlplane optimizations, for example via an NG-RAN. The UE and the AMF thenboth carry out a security setup via the NAS security context and carryout a ciphering and integrity protection procedure. The UE is then inIDLE mode. The UE can then transmit a Control Plane Service Request(control plane service type=“mobile originating request”,payload_container_type=“SMS”, payload_container [SMS message]) to theAMF. The AMF can then forward the SMS message to the SMSF associatedwith the UE, for example as a Nsmsf_SMService_ForwardSMRequest (SMSmessage) message. The AMF can then transmit a Service Accept (causevalue) message back to the UE and the UE can switch from IDLE mode toCONNECTED mode. An RRC connection can then be established between the UEand the AMF.

In some embodiments, a procedure for uplink transfer of multiple SMSmessages or a combination of SMS message and user data via control planefor user equipment in IDLE mode can be similar to that illustrated inFIG. 9, FIG. 16, some combination of the two, or a variation thereof.

In some embodiments, a procedure for uplink SMS message transport viacontrol plane for user equipment in IDLE mode can be carried out if theUE has an uplink SMS message to be sent. For example, if if the UE hasan uplink SMS messages to be sent, the UE can set the control planeservice type of the CONTROL PLANE SERVICE REQUEST message to “mobileoriginating request”. In some embodiments, the UE shall set the Payloadcontainer type IE to “SMS” and include the SMS message in the Payloadcontainer IE. In some embodiments, if the UE has additionally user datato be sent or multiple SMS message to be sent, the UE shall set thePayload container type IE to “multiple payloads” and include SMS messageand uplink user data in the payload container as individual payloadentry to be included in the payload container IE. For SMS message entry,the Payload container type IE of the payload entry can be set to “SMS”.For each user data entry, the Payload container type IE of the payloadentry can be set to “CIoT user data container”. In some embodiments, theUE can then send a CONTROL PLANE SERVICE REQUEST message, start T3517 (atimer) and enter the state 5GMM-SERVICE-REQUEST-INITIATED. In someembodiments, upon receipt of the CONTROL PLANE SERVICE REQUEST messagewith Control plane service type indicating “mobile originating request”,after completion of the 5GMM common procedures, the AMF can send aSERVICE ACCEPT message to the UE. In some embodiments, if the Payloadcontainer IE is included in the CONTROL PLANE SERVICE REQUEST messageand if the Payload container type IE is set to “SMS”, the AMF canforward the content of the Payload container IE to the SMSF associatedwith the UE. In some embodiments, the AMF can forward the content of thePayload container IE to the SMSF associated with the UE if the Payloadcontainer type IE is set to “CIoT user data container” and/or if thePayload container IE successfully passes the integrity check and the PDUsession ID is valid. In some embodiments, the AMF can forward thecontent of the Payload container IE to the SMF associated with the UE.In some embodiments, the AMF can forward the content of the Payloadcontainer IE to the SMSF associated with the UE if the Payload containertype IE is set to “multiple payload”. In some embodiments, the AMF canthen extract each payload entry and handle as above based on whether theentry type is “CIoT user data container” or “SMS”.

Referring now to FIG. 17, an approach is described by which userequipment in IDLE mode over a 3GPP access can have downlink SMS messagespending while the UE is using 5GS services with control plane CIoT 5GSoptimization, and for downlink transfer of SMS messages via controlplane for user equipment in IDLE mode. The process of FIG. 17 or anyportion thereof can be carried out by any suitable computing device,such as the apparatus of FIG. 1, and in particular one or moreprocessors in conjunction with computer program instructions stored onone or more memory devices. As illustrated, the process can include theregistration of user equipment with an AMF for CIoT control planeoptimizations, for example via an NG-RAN. The UE and the AMF then bothcarry out a security setup via the NAS security context and carry out aciphering and integrity protection procedure. The UE is then in IDLEmode. The AMF and SMSF can then establish an Association therebetween.The process can further include the SMSF transmitting theNsmsf_SMService_ForwardSM (SMS message) message to the AMF, after whichthe AMF pages the UE. In some embodiments, the UE will then, in responseto being paged, send the AMF a Control Plane Service Request (controlplane service type=“mobile terminating request”,payload_container_type=“CIoT user data container” or “SMS”,payload_container [user data or SMS], . . . ). The AMF will then sendthe UE a Service Accept (cause value) transmission. The UE will thenswitch from IDLE mode to CONNECTED mode. The AMF can then send the UE aDL NAS Transport (payload_container_type=“SMS”, payload_container [SMSmessage]) message.

In some embodiments, a process for downlink transfer of multiple SMSmessages or combinations of SMS messages and user data via control planefor user equipment in IDLE mode can include the AMF receiving downlinkuser data from the SMSF and initiating paging of the UE. In someembodiments, upon receiving paging from the AMF, the UE initiates aCONTROL PLANE SERVICE REQUEST. The control plane service type of theCONTROL PLANE SERVICE REQUEST message may indicate “mobile terminatingrequest” to indicate that an SMS message is requested to be transferred.Additionally, if the UE has uplink user data to be sent, the UE can setthe Payload container type IE to “CIoT user data container” and set thePayload container IE to the user data container. The UE can include thePDU session information (PDU session ID, PDU session status) associatedwith user data to be sent in the PDU session ID IE. In some embodiments,if the UE has uplink SMS messages to be sent, the UE can set the Payloadcontainer type IE to “SMS” and include the SMS message in the Payloadcontainer IE. In some embodiments, if the UE has both uplink user dataand SMS messages to be sent, the UE shall set the Payload container typeIE to “multiple payload” and include SMS messages and uplink user datain the payload container as individual payload entry as specifiedearlier in this section. In some embodiment, the process can furtherinclude sending, by and from the UE, a CONTROL PLANE SERVICE REQUESTmessage to the AMF, start T3517 (a timer) and enter the state5GMM-SERVICE-REQUEST-INITIATED. In some embodiments, upon receipt of theCONTROL PLANE SERVICE REQUEST message with Control plane service typeindicating “mobile terminating request”, after completion of the 5GMMcommon procedures, the AMF shall send a SERVICE ACCEPT message to theUE. In some embodiments, if the Payload container IE is included in theCONTROL PLANE SERVICE REQUEST message, if the Payload container type IEis set to “CIoT user data container” and if the Payload container IEsuccessfully passes the integrity check and the PDU session ID is valid,the AMF forwards the content of the Payload container IE to the SMFassociated with the UE. In some embodiments, if the Payload container IEis included in the CONTROL PLANE SERVICE REQUEST message, if the Payloadcontainer type IE is set to “CIoT user data container” and if thePayload container type IE is set to “SMS”, the AMF forwards the contentof the Payload container IE to the SMSF associated with the UE. In someembodiments, if the Payload container IE is included in the CONTROLPLANE SERVICE REQUEST message, if the Payload container type IE is setto “CIoT user data container” and if the Payload container type IE isset to “multiple payload”, the AMF extracts each payload entry andhandles in the same way as described earlier in this section based onwhether the entry type is “CIoT user data container” or “SMS”. In someembodiments, the AMF can include a downlink SMS message using a DL NASTRANSPORT message by setting the Payload container type IE to “SMS” andincluding the SMS message in the Payload container IE. If there are alsodownlink user data to be sent, the AMF can set the Payload containertype IE to “multiple payload” and include SMS message and downlink userdata in the payload container as separate payload entry, with each entryformatted to include Payload container type to indicate the payload foreach entry (same as when sent individually). In some embodiments, uponreceipt of the DL NAS TRANSPORT message, if the Payload container IE isincluded and if the Payload container type IE is set to “SMS”, the UEforwards the content of the Payload container IE to the SMS messagestack entity. In some embodiments, upon receipt of the DL NAS TRANSPORTmessage, if the Payload container IE is included and if the Payloadcontainer type IE is set to “CIoT user data container” and if thePayload container IE successfully passes the integrity check and the PDUsession ID is valid, the UE forwards the content of the Payloadcontainer IE to an upper layer (e.g., AMF, SMSF, or the like). In someembodiments, upon receipt of the DL NAS TRANSPORT message, if thePayload container IE is included and if the Payload container type IE isset to “multiple payload”, the UE extracts each payload entry andhandles in a similar manner as descried elsewhere in this portion basedon whether the entry type is “CIoT user data container” or “SMS”.

Message Control

In some embodiments, the CONTROL PLANE SERVICE REQUEST message is sentby the UE to the AMF in order to request transport of user data via thecontrol plane. The CONTROL PLANE SERVICE REQUEST message can containvaried content indicative of the type, payload, status, and othercharacteristics of the message, connection, or otherwise. A selection ofpossible contents for a CONTROL PLANE SERVICE REQUEST are provided belowin Table 3.

TABLE 3 CONTROL PLANE SERVICE REQUESTmessage content IEI InformationElement Type/Reference Presence Format Length ... Control plane serviceMessage type M V 1 request message identity 9.7 Xx Payload containertype Payload container type O TV 1/2 9.11.3.40 Yy Payload containerPayload container O TLV-E 3-65537 9.11.3.39 12 PDU session ID PDUsession identity 2 C TV 2 9.11.3.41 50 PDU session status PDU sessionstatus O TLV 4-34 9.11.3.44 F- Release assistance Release assistance OTV 1 indication indication 9.11.3.y 71 NAS message container NAS messagecontainer O TLV-E 4-n 9.11.3.33

In some embodiments, the payload container type IE can be included insuch messages if the UE includes the payload container IE. In someembodiments, the payload container IE can be included in such messagesif the UE has one or multiple data packets to be transferred. In someembodiments, the PDU session ID IE can be included in such messages whenthe payload container type IE is set to “CIoT user data container”. Insome embodiments, the PSU session status IE can be included when the UEneeds to indicate the PDU sessions that are associated with the accesstype that the message is sent over, that are active with in the UE. Insome embodiments, the Release Assistance indication IE can be includedin such messages by the UE to inform the network whether further uplinkor downlink data transmission is expected. In some embodiments, the NASmessage container IE can be included if the UE is sending a CONTROLPLANE SERVICE REQUEST message as an initial NAS message and the UE needsto send non-cleartext IEs.

The UL NAS TRANSPORT message can transport message payload andassociated information from the UE to the AMF. The UL NAS TRANSPORTmessage can contain varied content indicative of the message identify,container type, payload, connection/disconnection protocols, and thelike. A selection of possible contents for a UL NAS TRANSPORT messageare provided below in Table 4.

TABLE 4 UL NAS TRANSPORT message content IEI Information ElementType/Reference Presence Format Length ... UL NAS TRANSPORT Message typeM V 1 message identity 9.7 Payload container type Payload container typeM V 1/2 9.11.3.40 Payload container Payload container M LV-E 3-655379.11.3.39 12 PDU session ID PDU session identity 2 C TV 2 9.11.3.41 F-Release assistance Release assistance O TV 1 indication indication9.11.3.y ...

In some embodiments, the PDU session ID IE can be included in a UL NASTRANSPORT message by the UE when the payload container type IE is set to“CIoT user data container”. In some embodiments, the Release Assistanceindication IE can be included by the UE to inform the network whetherfurther uplink or downlink data transmission is expected.

In some embodiments, the DL NAS TRANSPORT message can be sent from thenetwork to transport message payload and associated information to theUE. An example of selected content from such a DL NAS TRANSPORT messageis provided below in Table 5.

TABLE 5 UL NAS TRANSPORT message content IEI Information ElementType/Reference Presence Format Length ... DL NAS TRANSPORT Message typeM V 1 message identity 9.7 Payload container type Payload container typeM V 1/2 9.11.3.40 Payload container Payload container M LV-E 3-655379.11.3.39 12 PDU session ID PDU session identity 2 C TV 2 9.11.3.41 ...

In some embodiments, the AMF can include the PDU session ID IE in suchUL NAS TRANSPORT messages sent from the network to the UE when thepayload container type IE is set to “CIoT user data container”.

In some embodiments, the “CIoT user data container” is a payloadcontainer type IE that indicates the type of payload included in thepayload container IE. The payload container type value (octet 1) caninclude 2 bits for an SMS message, 1 bit for a CIoT user data containerand 4+3+2+1 bits for multiple payloads.

The user data container IE can be used to encapsulate the user datatransferred between the UE and the network. As such, the user datacontainer IEI can be characterized, in some embodiments, as shown inFIG. 18 in which octet 1 designates the user data container IEI as such,octet 2 and 3 designate the length of user data container contents, andoctets 4-n contain or comprise the user data container contents (userdata).

In some embodiments, the SMS message container IE can be used toencapsulate the SMS messages transferred between the UE and the networkwith a maximum length of 253 octets (maximum of 2,024 bits). As such,the SMS message container IE can be characterized, in some embodiments,as shown in FIG. 19 in which octet 1 designates the SMS messagecontainer IEI as such, octet 2 designates the length of the SMS messagecontainer contents, and octets 3-n (where n is between 4 and 253)designate or contain the SMS message container contents (SMS message).The SMS message IE can contain an SMS message of any suitable type orprotocol, such as but not limited to CP-DATA, CP-ACK, CP-ERROR, amongothers.

In some embodiments, the Control plane service type IE can be added tospecify the purpose of the CONTROL PLANE SERVICE REQUEST message. Insome embodiments, the control plane service type IE can be characterizedas shown in FIG. 20. As such, in some embodiments, the control planeservice type IEI can be organized as one or more octets where octet 1comprises the control plane service type value (bits 1-3), a spare (bit4), and the control plane service type IEI (bits 5-8). As such, bits 1-3can be used to indicate a mobile originating request, a mobileterminating request, or otherwise.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe example embodiments in the context of certain examplecombinations of elements and/or functions, it should be appreciated thatdifferent combinations of elements and/or functions may be provided byalternative embodiments without departing from the scope of the appendedclaims. In this regard, for example, different combinations of elementsand/or functions than those explicitly described above are alsocontemplated as may be set forth in some of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

That which is claimed is:
 1. A method comprising: sending from a userequipment (UE) to a network entity of a communication system, a servicerequest message; starting a timer and entering a service requestinitiated state; changing a mode of the UE from an idle mode to aconnected mode; and initiating transfer of user data, to the networkentity, via a control plane, wherein said user data comprises cellularinternet-of-things (CIoT) user data in a CIoT user data container. 2.The method of claim 1, further comprising: including one or moreprotocol data unit (PDU) session identifications and one or more releaseassistance indications in a payload.
 3. The method of claim 2, furthercomprising: indicating a payload container type in a payload containertype information element (IE) of the payload, wherein the payloadcontainer type is a CIoT user data container type; and indicating thepayload container type to a user data container of the payload.
 4. Themethod of claim 3, further comprising: sending an uplink non-accessstratum transport message to the network entity.
 5. The method of claim1, wherein the service request message is sent from the UE to thenetwork entity in response to one of: the UE being in the connected modeover third generation partnership project (3GPP) access and the UEreceiving a paging request from the network entity, the UE being in theconnected mode over 3GPP access and receiving a notification from thenetwork entity with an access type indicating non-3GPP access, the UEbeing in the idle mode over 3GPP access and having uplink signallingpending, the UE being in the idle mode over 3GPP access and havinguplink user data pending, the UE being in the connected mode, or in theconnected mode with a radio resource control (RRC) inactive indication,and having user data pending due to no user-plane resources beingestablished for one or more protocol data unit (PDU) sessions used foruser data transport, the UE being in the idle mode over non-3GPP accessand receiving an indication from lower layers of the non-3GPP access,wherein an access stratum connection is established between the UE andthe network entity, the UE being in the idle mode over 3GPP access andreceiving a notification from the network entity with access typeindicating 3GPP access when the UE is in the connected mode overnon-3GPP access, or the UE being in the idle mode, in the connected modeover 3GPP access, or in the connected mode with the RRC inactiveindication, and in response to receiving a request for emergencyservices fallback from one or more upper layers of the 3GPP access. 6.The method of claim 5, wherein the service request message is sent fromthe UE to the network entity in response to the UE being in the idlemode, in the connected mode over 3GPP access, or in the connected modewith the RRC inactive indication, and in response to receiving therequest for emergency services fallback from the one or more upperlayers of the 3GPP access, wherein the method further comprises:performing emergency services fallback.
 7. The method of claim 1,wherein the service request message is sent from the UE to the networkentity in response to the UE being in the connected mode over thirdgeneration partnership project (3GPP) access or in the connected modewith a radio resource control (RRC) inactive indication, and in responseto the UE receiving a fallback indication from one or more lower layersof the 3GPP access, or when the UE has a pending non-access stratum(NAS) procedure other than a registration procedure, a service requestprocedure, or a de-registration procedure.
 8. A method comprising:receiving, from a user equipment (UE) or a session management function(SMF), at a network entity of a communication system, a service requestmessage; in an instance in which the network entity determines, basedupon the service request message, that the UE satisfies one or moreconditions, sending, by the network entity, to the UE or the SMF, aservice accept message; and receiving, at the network entity, from theUE or the SMF, user data via a control plane, wherein said user datacomprises cellular internet-of-things (CIoT) user data in a CIoT userdata container.
 9. The method of claim 8, further comprising:initiating, based upon the service request message and the user data, anauthentication and key agreement procedure or an extensibleauthentication protocol.
 10. The method of claim 8, wherein the userdata is stored within a payload, wherein the payload further comprisesone or more protocol data unit (PDU) session identifications and one ormore release assistance indications in the payload, wherein a payloadcontainer type is indicated in a payload container type informationelement (IE) of the payload as being a CIoT user data container type,and wherein the payload container type is indicated to a user datacontainer of the payload, the method further comprising: receiving, fromthe UE, an uplink non-access stratum transport message.
 11. The methodof claim 10, further comprising: identifying a PDU session routingcontext for the UE and the PDU session identification; and forwardingthe PDU session routing context of a payload container IE towards asession management function (SMF) identified by the PDU session routingcontext.
 12. The method of claim 10, further comprising: in an instancein which a release assistance indication IE is included in the uplinknon-access stratum transport message received from the UE, a downlinkdata expected (DDX) field of the release assistance indication IEindicates that no further uplink and no further downlink datatransmission subsequent to the uplink data transmission is expected, andthere is no downlink signalling or downlink data for the UE, initiatingrelease of a connection and mobility management (N1) interface on anon-access stratum signaling connection.
 13. An apparatus comprising atleast one processor and at least one memory storing computer programcode, the at least one memory and the computer program code configuredto, with the at least one processor, cause the apparatus to: send, to anetwork entity of a communication system, a service request message;start a timer and enter a service request initiated state; change a modeof the apparatus from an idle mode to a connected mode; and initiatetransfer of user data, to the network entity, via a control plane,wherein said user data comprises cellular internet-of-things (CIoT) userdata in a CIoT user data container.
 14. The apparatus of claim 13,wherein the at least one memory and the computer program code arefurther configured to, with the at least one processor, cause theapparatus to: include one or more protocol data unit (PDU) sessionidentifications and one or more release assistance indications in apayload, wherein the user data is stored within the payload.
 15. Theapparatus of claim 14, wherein the at least one memory and the computerprogram code are further configured to, with the at least one processor,cause the apparatus to: indicate a payload container type in a payloadcontainer type information element (IE) of the payload, wherein thepayload container type is a CIoT user data container type; and indicatethe payload container type to a user data container of the payload. 16.The apparatus of claim 15, wherein the at least one memory and thecomputer program code are further configured to, with the at least oneprocessor, cause the apparatus to: send an uplink non-access stratumtransport message to the network entity.
 17. An apparatus comprising atleast one processor and at least one memory storing computer programcode, the at least one memory and the computer program code configuredto, with the at least one processor, cause the apparatus to: receive,from a user equipment (UE) or a session management function (SMF), aservice request message; in an instance in which the apparatusdetermines, based upon the service request message, that the UEsatisfies one or more conditions, send, to the UE or the SMF, a serviceaccept message; and receive, from the UE or the SMF, user data via acontrol plane, wherein said user data comprises cellularinternet-of-things (CIoT) user data in a CIoT user data container. 18.The apparatus of claim 17, wherein the at least one memory and thecomputer program code are further configured to, with the at least oneprocessor, cause the apparatus to: initiate, based upon the servicerequest message and the user data, an authentication and key agreementprocedure or an extensible authentication protocol.
 19. A computerprogram product comprising a non-transitory computer-readable storagemedium having stored thereon computer-readable code, which, whenexecuted by at least one processor, causes the at least one processorto: send, from a user equipment (UE), to a network entity of acommunication system, a service request message; start a timer and entera service request initiated state; change a mode of the UE from an idlemode to a connected mode; and initiate transfer of user data, to thenetwork entity, via a control plane, wherein said user data comprisescellular internet-of-things (CIoT) user data in a CIoT user datacontainer.
 20. A computer program product comprising a non-transitorycomputer-readable storage medium having stored thereon computer-readablecode, which, when executed by at least one processor, causes the atleast one processor to: receive, from a user equipment (UE) or a sessionmanagement function (SMF), at a network entity of a communicationsystem, a service request message; in an instance in which the networkentity determines, based upon the service request message, that the UEsatisfies one or more conditions, cause the network entity to send, tothe UE or the SMF, a service accept message; and receive, at the networkentity, from the UE or the SMF, user data via a control plane, whereinsaid user data comprises cellular internet-of-things (CIoT) user data ina CIoT user data container.